The earliest "Operating Systems" as we call them today were developed at General Motors. The system was a standard stack of punch cards that would be executed with every program to take are of environmental tasks, provide a standard library, and standard I/O functionality.
This system was built for the IBM701 in '56, but was used on all 40 IBM704's that were sold. It influence the development of a lot of early 50's and 60's OS's nobody ever heard of now-a-days. Namely the Michigan Terminal System, which was very big and never spoken of.
This was still a batch processing operating system. But it was a far cry from the automatic tape switching Univac had only 2 years earlier!
Literally a rump kernel.
:.:.:
The ultimate problem with rump kernels is looking into the future, we arrive back at Unix. Follow the thought experiment.
1) We reach a standard rump kernel for virtualization, that support most users needs.
2) Its declared an industry success and sees wide deployment.
3) In order to speed up its functionality hypermanagers are ran on native rump kernels.
4) In order to speed up its functionality hypermanagers have rump features built in.
5) Duplicate rump features exist in the hypermanager, and its (the hyper-manager's) own rump kernel.
6) rump kerenels and hypermanagers are re-merged to multi-process OS's to remove duplicate code and offer speed ups.
What we need is a more multi-process OS, not a multi-user + multi-processing OS.
TL;DR we are back pedaling.