First of all, thank you for the positive feedback. We're happy that you like RDM and Wayk Now, even if you are not currently able to use it in production.
You are not the first person to request this feature, and it is already on our radar (see https://forum.devolutions.net/topic29752-someway-to-handle-uac-better.aspx).
To give you a better idea of where we sit with this feature, we need three separate enhancements to the product:
1 - Our protocol and client already support "remote execution" (where you can run processes and scripts on the remote system). We need to improve this to allow delegation of credentials; this would enable the equivalent of `runas`.
2 - Our remote execution feature also now supports downloading, validation and execution of binaries as of the 3.2 release. This needs further improvement to query and publish Wayk Now URLs.
3 - Client improvements to support reconnection to the newly installed elevated instance.
The first piece is the most complicated, but once implemented, that actually gets us most of the way there. There is significant utility in being able to execute processes and scripts under specific credentials on the remote machine in a secure fashion. It could even be possible to build the remaining pieces on top of that independently, with a properly crafted Powershell script to handle the remote download, installation and configuration.
At this point I can't make any promises, but we'd like to have that implemented - at least in part - in a release within the next six months. If it is only in part, it will be the first section mentioned above (i.e. the ability to remotely execute in the context of a specific user).
As always, please let us know if you have any further questions or concerns!