Using KeePassXC secret service integartion beetween VMs

[enmus]

Maybe this could be related?

KeepassXC security and single backend for all Qubes? (and healthy password management practices)

Since I am trying to master qrexec and make split-everything-socketable, I found it relatively easy to make a split-KeepassXC-browser configuration, where multiple browser instances in different Qubes may access a single KeepassXC backend. Are there any objections why it would not be recommended and I should stick to copying all the passwords manually (ugh)? I can disable it for most “dangerous” qubes anyway I also wonder if locking/unlocking the password database can be controll…