But I can give you some workarounds, as long as you promise not be upset when it changes later 
I will not, without change there is no progress!
Specifically, I will be making armoryd.py multi-wallet, just like ArmoryQt is. It will load all wallets in a given directory, and you will be able to "selectwallet", "getwalletinfo", "sendfromwallet", etc. Until then, I guess you'll just have to run multiple copies.
For a daemon it is a good thing if the functions "addwallet(filename.wallet)", "removewallet(wallet name or file name)" and "rescanwallets" are available. If you want the daemon run for 24/7 a restart (to load a new wallet or exclude one) is not preferred.
Also the memory requirements is a attention. I do not know how the memory requirement with ArmoryQT for a additional wallet works, but I expect it is not 1.5Gb for each wallet.
I think the last part is answered by my multi-wallet answer. If you have recommendations for how to accommodate multi-wallet armoryd that more intelligently, I'm happy to entertain it!
Yes you did, I will happy to do so and thanks!