Awesome release. Works great with Gateway. Surprisingly, it also gets Puma working too. You still need to point path.txt to a .bin copy to get reboot patches to work right, but, it works. Nice job. Now, if you could just figure out what Salt's hangup is, we'd have every A9LH payload working in B9S (well, I haven't tried converting Uncart or AGBSave9, but there's really no point). I know, Salt is currently dead because the author bricked his device. I'd offer to take it over, having a hard modded device and all, but I'm no coder. The closest I get are my non-keymapping AHK scripts for pseudo direct movement in non-import PC APRGs.
Just one question. If, say, I wanted to build a second copy that uses a different .ini file, what options would I use in firmtool? The example commands don't seem to work at all. In case you're wondering why, I'm using mini BootCTR9 configs to fix CFWs that aren't working in other chain loaders (again). CBM9 can patch it in memory, of course, so I've already got that working with separate .ini files that directly launch GW and Puma. But I'm anticipating having this issue with other chain loaders. I know, I should probably just be like "you're using BootCTR9, because it just works" but my AIO packs have always been about providing choices (which is why I was hoping someone had coded an updated A9LH installer for B9S, looks like no such luck).
P.S. It's good to see that some developers actually care whether their .bin build works or not (maybe if said A9LH installer existed, more devs would check them).