Did anyone tried to reverse-enginner this and find out how UWP is emulated to the machine during booting (how Windows setting up permissions and groups for C:\Windows\SystemApps,SystemResources and C:\Program Files\WindowsApps), how it isolates from the rest of the system, what kind of APIs (libraries) and executables takes from system and puts it into AppContainer so that every UWP executable will be able to find required files to be able to start itself.

I guess Windows 10+ explorer.exe takes many credits on this so starting from explorer.exe by Windows 10 or newer would be a good start to see how UWP applications are initialized, parsed and linked with libraries and permissions to actually be able to find required files and instead of crash to just start - of course that includes Windows.Universal family and other stuff about how it can detect if you're running Windows at all and on what version since even when we change device ID configurations, it still can detect somehow if we're Xbox One device or not so it seems that there is also additional configuration to the AppContainer that in it's own original way lets UWP apps know what device are you and on what OS version you're running and from what architecture.

If someone succeed in this, we could have a chance to implement UWP support to other systems like Linux (thanks to the Wine compatibility layer and similar wine-based projects for Windows execution support on non-Windows systems) or older versions of Windows that didn't comes with UWP at all (like Windows 7 or older) or even upgrading Windows Apps support on Windows 8.1 making it compatible to run with UWP apps.