Yes, NetBSD did accomplish that, but I expect it to become more commonplace.

but question is, is this solution for people running software on other peoples computers ? or solution for running my own code on my own computer only ?

For my particular case it's about something similar in purpose to sandboxing, but with providing the compartment (ie a process subtree) with an alternative kernel to talk to, to minimise the attack surface between that container and the host kernel.

Does it matter? Running kernel pieces in userspace is useful in both directions (rather like docker), and in both cases we'd like it to run as quickly as possible.