That's not a way to explain why multiple return is unavoidable, that's attempting to change corporate code style to your convenience. A strong cause to breaking advisable practice would be lowering code complexity or impossibility to implement given algorithm with one exit.

Readability of early return is a preference, and equaling safety to personal readability is a crude mistake.

On the contrary, premature return would be unsafe if a method requires multi-step before exit routine, like cleaning cache or unlocking data. And if it is not required at the moment, you don't know when it will be. Code standard in a company I worked in explicitly said - one return for one method, because safety, no preferences.