> To achieve our goal we use standard Linux technologies like containers (LXC) to separate the Android operating system from the host.
I don't know much about what Microsoft is working on, but "running Linux inside of Linux inside of Windows" probably isn't what they really want to do.
For a few years it may continue to be useful, however soon enough you won't be able to run a modern distro on WSL1. At this point it would actually be defacto deprecated.
Thus probably nobody, neither MS nor 3rd parties, will base a medium/long term plan on WSL1 now. It's already legacy tech; still maintained for essential things (security, etc.), but already legacy.
That's not quite the reason why it's deprecated. Microsoft can emulate a stable kernel's ABI for a long time before needing to update, so it's not the "fast paced dev" of Linux. The problem that Windows simply can't 100% emulate the behavior of all syscalls with the way NT functions. As a result, WSL1 will always be a subset of the syscalls available on WSL2. It won't matter if they don't keep up with new ones, however it starts to make WSL1 less useful over time.