Dependency on Explorer when process is fully elevated

I have an application using WebView2 to host its interface, the application is always running under Administrative accounts with highest elevation possible and its a requirement. By design WebView2 requires Windows Explorer to be running and initialized in order to be launched with lower privileges. My application run on Windows startup and this hard dependence on Explorer introduces multiple issues.

1. Web view is not usable if custom shell or no shell is enabled on the machine.
2. Hanged or not running Windows Explorer shell process instance can cause very long initialization times or total failures in WebView2.

This hard dependence adds multiple problems that is hard to overcome in order to have consistently working application.
There are multiple proposals given in various topics such as terminating\restarting explorer in order to recover failed WebView2 initialization but they are all prone to failure and just add more headaches for us developers.

I recognize that the dependence on Explorer is due to potential security risks but why not give us the developers a way to opt-out and just launch WebView2 process fully elevated?

There are plenty of users requesting this feature and other web engines that support such scenarios so why not WebView2?
I really hope that this proposal will be considered.

Thanks!