granted, that reduces the risk of real sensitive information being attached to linked accounts, but i’d still not be surprised if there are some accounts attached to them elsewhere if they didn’t get banned prior to receiving their first email.

i gotta admit i didn’t read the source earlier though, and i agree with your points in general for bot accounts if they have been banned before being used.

I’m sure proton would clear the inboxes before making the addresses available, so there’s no risk of seeing legitimate mail meant for someone else.

this is just completely wrong. obviously Proton wouldn’t grant access to existing mails, but the new owner of the address will still receive new emails intended for the previous owner. this is where the main risk lies.

there are most likely accounts with various services attached to these email addresses. you can discover some via data breaches, some via emails they send to you, and some you might discover via trial and error. it might even just be a service telling you that am account already exists when you try to sign up.

combine that with most services allowing account recovery by just using email, even for the services without publicly leaked passwords, you will be able to easily recover access to the accounts and in many cases get access to sensitive information.

that’s like calling strong randomly generated passwords 1.5FA.

with proper MFA, even if you steal my password (database), you won’t be able to steal my account, as you’re missing the second factor. with classic otp this is just a single use number you enter on the potentially compromised system, but if you get the seed (secret) stolen, valid numbers can be generated continuously.

password managers (should) protect against reuse. MFA protects against logins on untrusted and potentially compromised systems/keyloggers if they’re not extracted live. password managers with auto fill and phishing resistant MFA can prevent phising, although the password manager variant is still easily bypassed when the user isn’t paying enough attention, as it’s not even that uncommon for login domains to change. obviously there are also other risks on compromised devices, like session cookie exfiltration, and there is a lot of bullshit info around from websites, especially the ones harvesting phone numbers while claiming to require it for 2FA just to gaslight users.

FreeOTP/FreeOTP+

depending on your goal for this (real 2fa vs just simulated) you shouldn’t have sync in the first place.

you could also look into security keys (hardware solution, webauthn/FIDO2) as an alternative that has strong security with good user experience (no typing anymore), but they’re not as widely accepted.