boot a native MS-DOS 6.22 image (forget DOSBOX, if you want DOS functionality use fucking DOS!).
Well, depends on the use case. If you want to ensure your software will run on real DOS, you're right. However, in many cases, DOSBox will work better than native DOS. Run on DOSBox and never worry about not having enough conventional memory!
DOSBox will even let me install Win 3.11 drivers.
boot a native Win32 image with complete Win16 compatibility - just like you got in Win9x. Oh hell, I use win9x when I want that kind of functionality. Virtualbox lets me do that.
That's a good example of lagging development, actually. I have that need, but VirtualBox doesn't have Guest OS Additions for Win9x, which means incredibly slow and awkward performance. VMWare does have guest additions for Win9x, so I tend to use VMWare Player for that use.
do the above headless and feed a thin client or six, simultaneously, off a commodity desktop system.
Yeah, I suppose that's pretty nice. I can't vouch for it, because I haven't used that feature, but it sounds great.
let you export a disk image to a partition mounted via the host and thereafter, boot said exported image on a completely different piece of hardware with no further hacking required. I'm looking at you, DOSBOX.
Huh? DOSBox uses a folder on your box as it's C drive. Just copy that folder over to the new box, and you're done. No need to export or import anything. It's not like DOS has a registry to figure out what's installed, it just has config.sys and autoexec.bat, and whatever folders you installed things at. All of the DOSBox specific settings are really only about what hardware the DOS software sees, it has nothing to do with the host hardware (especially since the settings file now detects the CPU type you have and there's an auto setting for throttling cycles that works reasonably well). So you can copy the DOSBox settings file as well. If you use one of the many frontends, you can have a different configuration file for each game, which is another advantage over native DOS. I remember having an actual DOS Machine with a Turbo button because old games relied on clock cycles for their timing.
let you merge snapshots from specified thin clients into the service image while the image is in use.
Again, sounds impressive.
connect one remote session to another remote session from another server and directly collaborate between the two, migrating clipboard and keyboard events as you go, seamlessly between two completely different desktop environments as if you were hosting them both on the local system. Comes in handy on the odd occasion I'm moving bits of user data (eg user lists) between WAMP stacks that for some reason *have* to reside on the system partition and not the segregated data partition.
Can't vouch for it again, but sounds nice.