I’m support that and add the rule that in a situation where terminology and code are not populated, that this can be assumed to be a dv_text. That essentially flattens DV_CODED_TEXT and DV_TEXT and makes it much easier to handle for devs - if the UI returns a code, you must populate code AND terminology or you will get a validation error but if only value is populated and the element allows a DV_TEXT, that will be stored as DV_TEXT. No need to worry about different classes.
I think currently the Better format does allow : “X” :“some text” and does not like " “X|value” :“some text” for a TEXT.
I would continue to allow that as long as we are confident we can spot the stringified CODED_TEXTs.