"The user initiates a paste command manually" is a requirement that may be trivial for a human to express but near impossible for software to implement.
What? No.
Sure, there would be changes required, but both Android and iOS could support this pretty easily IMO.
"There would be changes required" is a very euphemistic way to phrase what would basically be banning all apps that don't use the high-level views in the OS SDK from having clipboard functionality. Funnily enough, if Apple were to come out tomorrow and say "we're removing the ability to cut, copy and paste from any and all apps that don't use UIKit" this website would have a field day tearing them to shreds and smugly posting about "walled gardens".
Convenience, freedom, security. Pick two.
Can’t think of anything else
1) I go to a site and it auto fills the login. Not sure when clipboard needs to be involved there. Shouldn’t that just be the application taking data from its database, recognizing the associated form, and filling it?
2) I search for a login manually and copy to clipboard. In that case I’d only ever want it to paste when I issue a paste command manually
- read clipboard
- write password into clipboard
- restore clipboard after X seconds
For example, if the implemented functionality is attempting to make a "temporarily store password in clipboard" feature and implementing it by "reading from clipboard/writing to clipboard/restore clipboard contents after N seconds", there should instead be an atomic "store data in clipboard temporarily" feature.