* IMHO save/don't save dialogs are an usability antipattern.
* Tray icons are also something of a remedy of the past. They are now replaced by background operations and live tiles. I can see why those can be problems, I can imagine the usecases you would solve using those tools, but the new app model is build around a slightly different workflow.
But if you do not like the way to solve it as it is intended in the new app model, the solution is: report it/upvote it. If you tell your problems here, then some members of HN community will know it and understand it, but it is unlikely that it will be acted upon by Microsoft. For that you need to have your voice heard on their forums. (eg. feedback app, uservoice...)
Of course not, because it's supposed to also work on mobile. Does your iPad let applications prevent you from going back to the home screen?
You don't see the problem here? Why do I want the restrictions of mobile phones limiting my desktop applications?
Bashing UWP for advocating a different app model, and different UI design principles is like still using bash in 2016 because you are accustomed to ash from the 70s, and GUIs cannot go to start of line with Ctrl-A, thus saying they are inferior. Change has its positive sides and drawbacks, but in both cases it is mostly for the better.
Sounds like you have some misconceptions about the UWP/WinRT application lifecycle:
https://msdn.microsoft.com/en-us/windows/uwp/launch-resume/a...
* No app closure callbacks. You don't know if it's suspending or exiting.
* No "are you sure you want to exit? Save/Don't save" dialogs. If you close or crash pray your data was saved, and if it takes a long time to flush to disk...really pray.
* No minimizing/backgrounding to tray icons allowed.