No, it’s all good anything to help.
But i really think it would be a great idea to have this feature!
I believe it would help out in hindering a attacker,data miner or speical interest groups from accessing any appvm or template if they found a way in or pass dom0 or found a way to jump from one appvm to another inspecting your system,layout,apps installed in appvm’s or sensitive intel. Thus then blocking access to any and all. With each appvm “domain” and template having its own unique and private password to enter that domain,template and appvm and no one is connect to each other to share the passwords between each.
You start up the template,appvm,domain…password promp popups before entering or i guess “starting” said area. Then it loads and runs.
This password for the said above could also be used as a “intrusion” alarm.
Lets say you online on one of your appvms doing whatever and lets say “attacker,data miner or speical interest group” has access to your qubes system without you knowing. Working in the background. And all of the sudden you get the “password” popup from one of the other template,appvm,domain asking for password to access. You would then know right then and there you have been infiltrated because some party other then yourself is trying to get in to it.