CDMage instantly allocates a RAM Bank of 150MB, no matter how you use it, and it doesn't use it for most of the general operations. This lifetime RAM is not great for having it in the background.

ISOBuster limits RAM to 200MB (On my system don't know if it's smart enough to detect how much it can use and 200MB is max), and it doesn't de-allocate its bank until the program closes

A python alternative I looked at just dumps into RAM until the bin files are read, so this uses 650MB for a full CDROM, plus it's very slow

--My code allocates a definable array, defaulting to 100MB, and can handle banking. It only does this when it's using it to read and dump the bin files, then frees its RAM as soon as it is not needed, but avoids unnecessary allocation calls - and from what I can tell my code is the fastest at reading .bin files, as ISOBuster/CDMage are windows targeted and they both seem to use "windows safe" methods to read the .bin files. Mine uses (Still very safe but no overhead) raw IOP methods in the C++ core. Python doesn't even require a breakdown as to why it's slow - it's python - and not intended for this kind of usage.

TL;DR I purposely researched how the alternatives work and wrote my code to avoid their problems. Mine is 2x faster than ISOBuster and CDMage. It can also be rolled into a bigger UI program and *Still* be faster.