Yeah, OK
Yeah, OK. If they build single-purpose VMs with custom kernel as opposed to "containers", just brainstorming, they can have:
Custom kernel, it knows it's running on VMWare, so it only needs to probe for hardware VMware actually supports. Paravirtualized hard disk and network, and tickless (although I think most kernels do this by default anyway.) Take out unnecessary time delays from the kernel (that real hardware may need but virtualized doesn't... like delays while probing PCI bus, USB, delays for disks to spin up or "settle", and on.)
Custom userland... customized bootup, you can have a pretty minimal init that just runs whatever the container/VM is supposed to run. And only whatever libraries the particular application you are running needs. I think some containers already do this -- if you just containerize a whole Linux install you've got a GB or 2 of stuff in there, but if the container contains only needed libs it could be under 50MB.