How exactly are you sure that the email is encrypted and is read only by the intended receiver and not by anyone else? This is too simplistic as a solution. Things like what to do if a user clicks on the same link more than once also have to be considered (is it really the intended user who clicked it or a malicious actor that the user is not aware of?).
One way this has been prevented for me so far is to include a one time pass in the mail along with the link, but some people might still not have a second device on hand every time they want to log in.
Same way you make sure that the password reset links sent to your email are only received by you and not by anyone else?
I wish every site did this. Especially for non technical users, passwords are such a mental barrier.
Edit: Even if it's an account held on a private server, there must be a password, must there not?
Point is, this advice is probably aimed at developers who aren't working on email systems.
We also AES encrypt the emails with the key stored on a network share. It doesn't add a lot of complexity and if an attacker gets hold of the contents of the database, they still don't have this piece of PII. It's by no means a big hurdle against any serious attack but it's nice to have.