I am happy to report that after my post on here a developer has reached out, and the issue is indeed fixed for me in the latest nightly build of 1Password. Seems like this issue can finally be wrapped up :)