Moved to Feature Requests.
When people like @george1421 say things like “oh that’s easy, just carefully do this then this then this then this…” Chances are they can get it done within a few hours.
I myself don’t see how it’s easily possible because not all ISOs work exactly the same. The kernels are in different directories, inits might be in different directories. Some might just flat out not work with NFS like WinPE or similar. I got a DBAN ISO to work across HTTP for instance… While the NFS method might be easy to automate for the mounting and menu entry aspects - All the ohter aspects will prove to be very difficult to script… just because there are so many differences across different ISOs.
That and… it’s not the intention of FOG to deliver ISOs on a boot menu. The intention of FOG is to create a seamless imaging environment and to reduce the workload associated with that imaging. Anything extra is a big bonus.
The @Developers have already provided a highly advanced boot menu editing system. That’s their way of saying “Here, use this for all that other stuff you want to do.”
