E.g. resolution enhancers on Falcon, some has to run after MiNT and some before.
But you don't need such things when running in an emulator.
Running NVDI after MiNT does not work, atleast not on any of my machines.
It works when you only need the GDOS part of it. I do that occasionally, and use fVDI at the same time for the screen driver.
Boxkite must run before MiNT
Boxkite was always problematic, even on plain ST.
while the Afterburner/Milan/Hades FPU-emulation has to run *after*.
Same as above. No need for such things in an emulator.
Feel free to install and modify VanillaMiNT on any kind of hardware or emulation, it can be fettled to work on "anything" but you're on your own
That might be true. I cannot tell how i would call my installation, basically it is a self-compiled MiNT kernel, and configuration files adjusted to my needs. None of this would work on real hardware, and it took me some time in the beginning to figure it out. But having everything on the host side has the big advantage that you can edit the configuration files there, without the hassle to mount/unmount the boot disk image every time, maybe even having to byte-swap it first before doing so.