We are striving to make civil survey the premier package that allows you to import, process and edit your survey data and prepare it to be sent as your deliverable. We are always looking for ways to improve our product. You mention that certain edits can only be performed by exporting back out to the native raw file and re-importing. I would be interested to learn about these required edits so that we can look at the possibility of adding them to the our edit tools.
Regarding the alpha codes such as MISCDNC, MISCPT, etc: No part of a FEATURE DEFINITION Name may contain a linking code. For example, if you have a FEATURE DEFINITION “STEPS” then that will conflict with standard linking code “ST” If this is the case for your data, then you can change your linking codes to be unique like .ST .PT .SC etc. Then you could use String Substitutions in Survey Project settings to replace “ ST” with “ .ST”, “ PT” with “ .PT”, etc.