This argument (which has come up repeatedly) is based on a double assumption, namely, that people who understand the difference between the various dashes and care about it will use U+2010 HYPHEN (and U+2013 EN DASH and so on), whereas the other will use U+002D HYPHEN-MINUS. However, both parts of the assumption are wrong.
- There are lots of people who know of and care about the difference between en-dash, hyphen etc., but will still type the hyphen as U+002D HYPHEN-MINUS because they think this should be the preferred code point for the hyphen. (They will use U+2013 EN DASH, U+2014 EM DASH etc. where appropriate, of course.)
- On the other hand, people who have no clue or don’t bother won’t specifically use U+002D HYPHEN-MINUS. Instead, they will use whatever is most easy for them to type or copy-and-paste. That may or may not be U+002D HYPHEN-MINUS.
Therefore, this idea of using U+002D HYPHEN-MINUS as an indicator of “needs review” and U+2010 HYPHEN, U+2013 EN DASH etc. as an indicator of “has been reviewed” is seriously flawed.
I also don’t understand why we should want to use such flags for the hyphen/dashes issue specifically. After all, we don’t ask people who are bad at spelling to mark the track names they enter with some special character, either. And even if we did, the people who would most need to use such a “needs review” mark wouldn’t be aware of that (Dunning–Kruger effect).