There's nothing you can do "officially" in the UI that I can think of. But updated() is called when "Save Preferences" is clicked, so you could do some validation there and display an error message in the UI (on a dynamic page) or in Logs (pretty easy, even if not as intuitive for users) if your validation check fails then.
I was thinking of something similar to the "required" field that already exists and checks for an empty input may be running in a way that can be asked to run something in addition.
With submitOnChange = true, no need to wait for updated. Validation code can be called performed any time, tho performing validations in the code prior to page sometimes causes problems with settings variables or calls to parent. I like to perform validations to disabled app saving, then either do them again later, or save the results, to display an error message.