Well, that's not exactly the reason, although we you are probably right - a more general assumption is that we try to keep our default hosted service as simple as possible. You know, the more moving parts a system has, the more it is prone to errors and malfunction.
Whereas with RU Server we can experiment and add more advanced features. By the way, using e-mail for what you described is probably overkill. If both Host and View keep connection with the RU Server alive a notification (or a desktop alert) could appear right in the Viewer. So we'll give it a thought and adjust our plans regarding the RU Server roadmap accordingly.
Remote Utilities only transfers the print file from the remote PC to the local PC in a special printer interchange format, understood by all printers. When printing the file to your physical printer on the Viewer side did you play with printer options in the standard Windows Print dialog?
Both these options can only be possible with RU Server rather than with our default (corporate) server, for obvious reasons. We'll take a look at your suggestions and see if we can implement them in subsequent releases.
The possible explanation is that when you restart using Power Control mode in RU, forced restart is used. That is, even if there's an unsaved work/document or unfinished process on the remote PC, the system will restart anyway.