Unfortunately Richtext, Text Description fields etc. all seem to simply remove actual raw/pure text-data. The only thing coming close is pasting text-data (that contains classic/newline characters) etc. into a code block as (pure text) within a richtext data field.
It would be beneficial to somehow enable “retention” of actual text data. (Including \n) etc. over any sort of stripping or richtext conversion. As this would enable workflows based on text-based, single-entity creation. As well as potentially data-aggregation or splitting via regex and formulas.
This new (?) type of “pure text” data field might also enable processing, conversion between richtext/puretext or other template/html types.
It would enable/simplify parsing, splitting and processing of classic (or message-based) text data (based on \n and other, non-csv denominators): Unlike a chunk of single-line, escaped text without any original control-characters. Not sure how that side of things works in common “markdown”. (If that’s even possible) - but if there is a way to detect newlines/controls in markdown/richtext. That would also be a great option. I feel like that’s probably one of markdown’s biggest limitations.
It would also enable text-based data without having them (inaccessible?) within richtext/markdown, richtext-codeblocks and text files or attachments.
It sounds like what you want to do may already be possible. The contents of rich text fields can be accessed (either via the use of rich text snippets, simple text fields and regex, or using scripting).
If you provide a specific example of something you want to do, maybe we can brainstorm the options