I really like the idea, but I think this may also cause issues with obscure software.
I think using [apisetschema](https://gitlab.winehq.org/wine/wine/-/tree/master/dlls/apisetschema) (like) implementation to forward the dlls to winewinrt could be a good idea to handle thoses cases.
Also you forgot to move `windows.ui.dll` to your implementation, which is also a winrt dll.
Furthermore the fact winetrick can change which dll to load which class also already allow winetrick to create workaround for
Also you may also want to semi-implement [`wintype.dll.RoResolveNamespace`](https://gitlab.winehq.org/wine/wine/-/blob/master/dlls/wintypes/main.c#L358) as it's used by dotnet to know which class to use, which make current winrt not usable by most winrt applications. (I wanted to do it for a long time, but because of health issues I am unable to do it, and I don't think it will be solved for a long time, so please do it for me if you can)
Having a working [`wintype.dll.RoResolveNamespace`](https://gitlab.winehq.org/wine/wine/-/blob/master/dlls/wintypes/main.c#L358) is a known (but not only) requirement to run the Minecraft Windows10 launcher.