I am not trying to imply that fixing these bugs will be trivial.
But that “landscape” import-export pipeline seems to have a number of strange “features”. At least the validation or postprocessing code is missing some obvious steps/checks.
So if Asobo figures out what is going on then that would automatically fix … well … most likely all regions where they will be running a 3D scenery refresh.
In some way I would even suggest/assume that there is a relationship to bugs like …
… as those 3D spikes are also an artifact of 3D data mismatch which is not automatically detected by the processing pipeline.