I think it is better, if it will override all, IF the ELF is present, it WILL BOOT EVER!
This will make it also easy to No-Mod-Users, if they were not kicked to patched OSD (where you can restart it directly/1.4c-BETA-Feature) or hanging on a BSOD.
That's why I thought about the RESCUE.ELF.
If there is a typo, or bug within the sequence, it'll stop before the ELF starts, which makes no sense, if it should be the "last heaven" to rescue your FMCB.
If someone misses the CNF, or bugs occur in newer versions and the user is not able to recreate FMCB, it'll be possible through the RESCUE.ELF .
If it isn't found, it will do the rest like normal.
Only one new file, it should EVER search BEFORE (else it wouldn't match the point, what it was intended for) it starts.
If it isn't there, it should going further with the rest of the process.
If it is there, it should start it.
Btw: "suloku" will also happy about it I think, because it EVER starts and give him the "Freedom" to Auto-Start an app (even, if it is intended only for Rescue-Service), even if the Fastboot-Feature is on and a disc in drive.
If you want to go back to configured Settings, just plug in the USB-Stick.
I think FMCB is intended for this also:
-Work on most/all Versions
-Give highest compatibility that is possible.
-Give high flexibility, while also a Standard/Hardcoded-Mode, without a CNF.
PS2 V7/DMS3 V2 (FW:2.4b7); Seagate Baracuda 200GB
PS2 V7/CC1.0 (FW:34 hacked v2 BM:2.1.6); Maxtor DiamondMAX9 PLUS 160GB
PS2 SCPH-30004R; NoMod+NoLaser
3xSony MC 8MB
MAX/Datel 16MB with Boot-CD
Custom FMCB 1.8b+ Beta-Build, my AIO 0.5, Sony&xRhino-Linux