I mean. It's built on KVM and integrates deeply with how processes work; I'm not sure it's possible to make it portable without a lot of engineering time, performance hit, or both.
What you described is absolutely what happens when you run Linux containers on Windows hosts using Docker.
What I linked is absolutely a Docker image that contains Windows, intended to run Windows containers on Windows hosts using Docker.
Windows containers are Microsoft's attempt to clone Linux containers. They can run in one of two modes: A shared-kernel mode, which requires that the kernel of the container and the host OS be the same version (with some kind of Windows filesystem namespacing), or a separate-kernel mode, which essentially uses the Docker image distribution ecosystem as a way to distribute system images to run as VM's on Hyper-V. Windows containers are super-clunky and I believe they aren't supported on the latest versions of Windows. Honestly very few people should use them. But they do exist.
it's worked for "run this docker to use this code" sort of things on windows for me. That's all i use it for, it's an inconvenience. Docker, that is. Not docker on windows. Docker in general.