MacOS – How to change a filetype’s “Kind” value in the Finder

You could make new CFBundleDocumentTypes entries in /Applications/TextWrangler.app/Contents/Info.plist. Many extensions are currently defined under a single entry with the CFBundleTypeName TextWrangler text document:

<key>CFBundleDocumentTypes</key>
<array>
    <dict>
        <key>CFBundleTypeExtensions</key>
        <array>
            <string>a</string>
            <string>as</string>
            <string>asm</string>
            <string>asp</string>
            <string>bashrc</string>
            <string>c</string>
            <string>c++</string>
            <string>cc</string>
            <string>cfm</string>
            <string>conf</string>
            <string>cp</string>
            <string>cpp</string>
            <string>cshrc</string>
            <string>css</string>
            <string>cxx</string>
            <string>equ</string>
            <string>erb</string>
            <string>f</string>
            <string>f77</string>
            <string>for</string>
            <string>ftn</string>
            <string>h</string>
            <string>h++</string>
            <string>hpp</string>
            <string>htm</string>
            <string>html</string>
            <string>inc</string>
            <string>j</string>
            <string>java</string>
            <string>js</string>
            <string>json</string>
            <string>jsp</string>
            <string>log</string>
            <string>m</string>
            <string>mm</string>
            <string>p</string>
            <string>pas</string>
            <string>pch</string>
            <string>pch++</string>
            <string>php</string>
            <string>php3</string>
            <string>pl</string>
            <string>plist</string>
            <string>plx</string>
            <string>pm</string>
            <string>ppu</string>
            <string>profile</string>
            <string>r</string>
            <string>rb</string>
            <string>rez</string>
            <string>rhtml</string>
            <string>rss</string>
            <string>s</string>
            <string>sql</string>
            <string>shtm</string>
            <string>shtml</string>
            <string>tcl</string>
            <string>tcshrc</string>
            <string>text</string>
            <string>txt</string>
            <string>wml</string>
            <string>xhtml</string>
            <string>xml</string>
            <string>xsl</string>
            <string>xslt</string>
            <string>yaml</string>
        </array>
        <key>CFBundleTypeIconFile</key>
        <string>TextWranglerTextDoc.icns</string>
        <key>CFBundleTypeName</key>
        <string>TextWrangler text document</string>
        <key>CFBundleTypeOSTypes</key>
        <array>
            <string>TEXT</string>
        </array>
        <key>CFBundleTypeRole</key>
        <string>Editor</string>
    </dict>

As usual, making changes inside the bundle invalidates the code signature. A new certificate can be assigned with codesign -f -s - /Applications/TextWrangler.app.

There is not a safe and advisable way to achieve what you are after because this function of the OS is controlled by the Launch Services database. Developers register the filetypes their applications support with the OS on first launch.

The best way to get this fixed is to petition the developer to add support for the file extension in a future version of their application.

With that said you have already found the only documented way that Apple offers for overriding the edicts of the Launch Services database. If you want to dig deeper and take the road less traveled supported here are a few pointers.

There is a .plist file that governs part of what Launch Services does located at: ~/Library/Preferences/com.apple.LaunchServices.plist

Apple notes that removing this plist can clear out unwanted Open With contextual menu options. But that's the opposite of what you're after.

It's a binary .plist but you could convert it to an xml version and experiment a little to see if you can come up with a recipe to achieve what you're after. This isn't advisable, it could cause harm, and it will most likely get overwritten by the OS at some point.

There is also a tool hidden a bit deeper in the OS called lsregister which could be helpful in exploring Launch Services's plumbing. Here is a helpful explanation of lsregister and its options.