About "load_custom_payload". Don't forget that not EVERYONE is on CFW 3.55 or even on 3.55.
Using a regular 3.00-3.41FW + JB USB and all is working just fine. I added the option to disable the built-in LV2 payload injection. You can still do it with external program.
LV1 = HYEPRVISOR
LV2 = GAMEOS (resident memory / RAM)
LV1 PEEK/POKE allows you to read/modify LV2 (GameOS) via LV1 (Hypervisor).
LV2 PEEK/POKE allows you to modify LV2 memory *GameOS" directly.
Since FW 3.55 has memory protection (LV2 memory protected) - one needs to disable the protection, so LV1 is changed to disable the protection and then payload (or other modifications to GameOS) can be performed.
lv2.pkg is a program which removes LV2 protection (via LV1 hypervisor) and then changes the GameOS memory (LV2).
The problem is that it is a dirty hack and causes a lot of freezes.
multiMAN can run in regular retail mode without JB or CFW. In this mode you can do EVERYTHING except mounting game backups to /dev_bdvd or /app_home.
A regular JB (payload) allows you to 'remap' folders and install PKG files (signed or unsigned).
I added some kind of "save last state" for multiMAN. It will save the last display mode you used, the font, overscan, content mode and "show paths" options. By doing this - it will save time editing the ini because upon next multiMAN launch you'll have everything as the last time you left it.