You are splitting hairs. It outlaws passwords where only the (salted) hash and not the plaintext is stored, which is the whole point of what's commonly known as "hashed passwords".
store the hashed value with your live database ... and store the plain text version in ... a separate system
Call that seperate system "the moneypot". I'm tempted to suggest that people just try that and see how that works out for them, given the inevitablity of failures of security and vigilance. But for the sake of the rest of us, let's not.
If someone has that level of control over your system to access a write only file on a separate secured system, make a copy and extract it somewhere else, they probably also have enough access to insert a piece of code into your authentication system to dump all the plaintext passwords to a separate file as people login over time.
The message remains the same for all users regardless of this law - Don't reuse passwords, you can't trust their security.
of course you aren't. We know this because you say you aren't. What you are is making a nuanced distinction between what you mean when you say "stores hashed passwords" and what is commonly meant by that.
It's totally legal to store the hashed value with your live database as normal to provide authentication, and store the plain text version in a write only file on a separate system to try and give some additional level of security. This isn't a great solution, but it does provide hashed passwords for regular work, and plain text for when the police ask for it.
It's obviously a pretty stupid law, but to say it "outlaws" hashed passwords is just nonsense.