Configuration checking suggestion (colon space check)

Could the configuration checker be configured to make sure that the FIRST instance of a colon on any given configuration YAML line be followed by a space?

Would that violate some valid configuration scenario?
I hope not, because it would save me a lot of time searching all my configuration files for devices not showing up in the frontend because of “some line above it” that was misconfigured.

Regardless, thank you!