What is really needed is a next-generation NumberDisplay, with an API that is better suited to displaying a string that is derived from a TReadOnlyProperty<number | null> and other dependencies (like translated strings, preferences, etc.)
NumberDisplay is a widely-used UI component (43 imports across the PhET code base), so it seems like this should be relatively high priority.
NumberDisplay has reached its end of life. It is not a good fit for the current PhET feature set, especially dynamic strings.
As I commented in https://github.com/phetsims/scenery-phet/issues/824:
NumberDisplay is a widely-used UI component (43 imports across the PhET code base), so it seems like this should be relatively high priority.