In the "Minimize Feedback / Information Exposure" section, you write:
If a user tries to create an account using an email address, don't tell the user if an account with that email address already exists. [...] Providing that information would allow an attacker to determine if a specific email address is being used (or not) by some existing account.
I definitely see the point, but I'm not sure what the correct reaction would be.
I guess you could pretend to make the account, and end the flow with "Please confirm your account creation in the mail we sent you." and instead send a mail explaining that you or somebody else tried to make a new account with this mail despite one already existing? Or maybe just display a message like "If there isn't already an account registered to this email adress, we've sent you a mail!" similary to how you'd implement password reset?