If you're confident in your Python programming skills (i.e. you don't mind modifying what someone else hacked together), then I could share the Webpage Maker's code with you (use the email in my last PM). I'm not sure an elegant solution could be implemented, but my investigation into your issue has made me aware that (I think) a modder could make a runeword for Helms, but make it so that the runes gave shield-mods in Crowns but weapon-mods in Caps. I might have to take a look at the runeword-page generator some more some day, I think that project will take quite a while though.
As a quick-fix for your situation (probably take quite a while to setup (an hour?), but just a few minutes to update in the future):
I've taken a quick look at your files, it looks like Glove, Belt, Boot count as Torso/Helm runewords.
- Considering runes.txt allows you to copy a runeword's row completely, you should make sections in your master file (e.g. belt, glov, boot, helm, tors, shld, weap; or just belt, glove, boot, EverythingElse), so if you have a runeword for Gloves and Torso, just copy the runeword to each section (updating both sections separately if you change the runeword's mods). This means you'll only need to use the itype1 column.
- Once you've got a section for each type, make copies of runes.txt, one copy per item type, store each in it's own folder along with a copies of gems.txt, properties.txt, and the webpage maker.
- In the folder for BootRunewords, delete all non-boot rows from runes.txt.
- Replace all instances of "boot" with "helm" (or "tors")
- Run the webpage maker. It will generate a small runewords.html with runewords just for boots, you could rename it.
- Open the boots-runewords.html and replace all instances of "Helm" with "Boot".
- Repeat steps 3 to 6 with the other runeword item types, but you don't need to worry about steps 4 & 6 for helms, shields, weapons, torso.
- You could share the final runeword web pages as either separate files, or you could copy-paste parts of the html of some pages back into a single page (maybe with html anchors and links to navigate sections).
- In your future updates, after you've modifed the master runewords file, you could just highlight the edited section, and copy it to the runes.txt file in the relevant folder before repeating steps 4 to 6
There are other solutions where you don't make the separate folders per item type, but I'm pretty sure that's the best way for you to go (alternatives wouldn't let you trivially rename "Helm" to "Boot").
I might have time to do this later, just to confirm that nothing unexpected would happen or that I haven't forgotten a step, but it might be a couple days. I'm pretty sure you can have completely blank rows in runes.txt in order to make the section separations more clear.
<edit>I got around to doing this (
pages for Belt, Boots, Gloves, EverythingElse (up to you if you want to continue the pattern into separate Shield, Armor, Helm, Weapon pages)), and it seems like it'll work without much future trouble. Once you've made edits to the main runes.txt file, you'd have to copy-paste rows into the runes.txt files in each runes-subfolders, make the webpages in each subfolder, edit the html files (you can use "replace all" if you're swapping "helm" with "boots" "gloves" "belt", so this shouldn't take more than a minute each), and after that you might be done or might edit html pages some more. I've run HU Renew 1.0.6 with -data -txt and confirmed it generated runes.bin without showing errors in the debuglog.
I didn't see a pattern in the main runes.txt list, so I sorted things by RuneName (I kept the binding of "Name"+"RuneName" but didn't confirm that they actually matched in-game ("RuneName" is only viewed by modders and the webpage maker)) and re-generated the runeword field (only viewed by modders anyways, but a nice reminder when it's accurate).
</edit>