PROOF
1. Though the 2.3 payload upon execution does relocate itself to
0x80000000007f0000 then continue execution, the USB descriptor is
still present, at minimum those 0x20 bytes would need to be removed,
or accounted for during the initial execute. multiMan has no facility
for this.
2. The initial EBOOT.BIN.elf does contain the 2MB flash contents for the
dongle, BUT that would need to be carefully extracted (and has been, it
too is available on the ps3devwiki), again multiMan has no facility for
this.
3. The creating of the folder and copying the files into it was just to
make this fake seem more real with additional steps. multiMan has no
code to ever look inside that directory.
4. The fact of the matter is that the source code for multiMan was
available, and there is NO provisioning in multiMan for "additional"
payloads of any kind, the values possible in the .ini file are
hard-coded. It is well documented what payloads work with multiMan,
and multiMan will only work with those payloads.