No, but that’s the topic of the discussion started by Branais.
Exporting from one program and importing to another is apparently not as easy as one might imagine. That’s why I think it is best avoided. If you’re exporting to Truetype outlines it would be best to draw with Truetype curves, and with Postscript curves if exporting to CFF postscript outlines.
Scripting might be hard to implement, but Erwin has said that it should not be difficult to make transformations proportional. Scripting may be fast, once you have taken a few hours to write the script. Take a look at CompositeData.xml. That saves a lot of work, but it took a lot of writing and testing. It’s still far from perfect.
You don’t have to look far to see that I am well aware of the work caused by Transform scripts being limited to absolute transformations. I think that scaling transformations proportionally to the stroke weight will remove most, if not all, of those crossed knots resulting in much less work fixing errors.