A display can only have one child.
What you are doing is replacing the child of 313.
Which during 3DEN preview is DisplayMission, you are deleting the mission display while playing the mission.

@BIS_fnc_KK wrote a fix.
Just automatically find the last child and add the new display to that one instead of adding as child on the display that you requested.

Actually this is much more troublesome...

Currently, "parent createDisplay" is the same as "deleteDisplay child parent" followed by creating a new display.
So scripts can use that to delete displays, and as we don't know what modders might've written in their scripts, there might be scripts that intentionally do that that we would break with this change...

We can try to only do this fallback in cases where you delete the mission display as we know that will go wrong.
And there should also be a displayChild script command so that you can check for yourself if your createDisplay will be destructive.

So fix is this

parent = findDisplay 313;
wouldDeleteDisplayMission = false;
currentChild = displayChild parent;
tempParent = parent;

while (!isNull currentChild){
  if (tempParent is "DisplayMission")
    wouldDeleteDisplayMission  = true;

  tempParent = currentChild;
  currentChild = displayChild tempParent;
}
if (wouldDeleteDisplayMission)
  parent = tempParent;

parent createDisplay "RscDisplayEmpty"

I think this is the best way to handle this, while not breaking backwards compat in any way.
We know that NOONE is doing this with DisplayMission intentionally, because it crashes the game. So fixing this won't break backwards compat.