If you see the ".:rei" string in system settings then they are all loaded. If not then loader.cxi isn't in "SD:/rei". If you haven't deleted anything in /rei then you are fine.
So, will it run without "loader.cxi" now? The previous version would crash without it. Which threw a wrench into my "stealth mode" feature that launched ReiNAND without it to have a relatively legit looking system (in case they decided to check systems for CFW at a Pokemon tournament or something). So, I had to comment the line that moved it out. If it works without it again, that's good news for people who want such a feature.
Also, only one of the .rnp files got included in the "patches.dat" that is in the release. It's a bug with the Windows versions of the compilers, I think. I get around it by having a batch file do the compiling, and having it delete the generated "patches.dat" file and use "copy/b" to create one that includes all of the .rnp files. It should be 115 bytes, not 18. Unless "loader.cxi" handles those other 3 patches now.
It would be easy to write a GM9 script to extract the firms (we're talking less than 30 lines). But is this only for EmuNAND? Or will it use the extracted files for both, if present? If it's only using them for EmuNAND, would it not be better to have the script extract the firms from said EmuNAND, so that the EmuNAND is being run with it's own Native FIRM instead of the 11.4 one? That just seems like it would provide better compatibility. Well, let me know which would be better. I'll post a standalone version here, then I'll probably add it to my "Settings" app (seems like the most appropriate place for it in my AIO, but I'm open to suggestions).
Nope. There is an extra step for emunand users though. You will have to get your own firmware binary files. But I made instructions for that on the Readme as well as add the file 'loademunand' with no file extension to the /Rei folder. But you just install b9s and can use Rei-Six. But it is recommended that you just abandon emunand. Emunand isn't required and just takes up space. Keeping a 9.2 firm is also quite irrelevant since you can hack the latest firmware using a DS flashcart. SysNands older than 11.4 can't boot on Rei-Six anyways.
You're forgetting about Gateway for ROM loading, for those of us who still use it (if you have a large ROM collection like me, multi-booting into GW is much less of a hassle than converting everything, and even if it never gets another update, GW will still run most ROMs just fine). Unless they finally put out an update while I wasn't looking. It's not like the Dragon Quest series is multiplayer anyway. So that stuff can go on my second card.
And I like keeping 9.2 around for old exploits. But that's my second one with me being a GW owner. Meaning I can't use ReiNAND for it anyway. But Puma and Luma Legacy work for that (and Cakes on the O3DS, but it only supports 9.2 SysNAND on the N3DS for whatever reason). I like having Ninjhax 1.1b still available just in case. And I like being able to chainload into Menuhax. Not that having one of my alternate CFWs boot an EmuNAND that more or less goes straight into the HB menu is a necessity, but it's a nice convenience if you have a big card and space to burn. But yeah, it's pretty much just a power user thing. Not something most people will miss.