No difference with dual emunand or PBT-CFW. It's only a front end that can avoid swapping files on SD.
I already started to write a commented version of the boot.bin decompilation, and probably I will release it so someone else can try to fix the code.
But probably it's woth to follow a different way, like using the newer firmlaunch code (that you can find on Roxas github) instead of the old one used in the CFW or in the fist version of GW code. It should be easy to insert it in this launcher.
Everything is already out there, we miss only good coders (I'm not a good coder as you can understand reading my code
and have very few time)
At the moment I don't have anymore a 3DS for coding and my child don't want I use theirs too often
.
Maybe if I find a used 3DSXL with 4.x Fw at good price, I could buy it and play a little more with this CFW. My idea was to add an option to setup the emunand from the 3DS, like the GW SW does, with the option to select between GW and CFW emunand format, emunand extraction and injection, second emunand setup, partition resizing without loosing SD content. Nothing difficoult to do with low level SD libs you can find in rxTools source code.