(Visual Scripting) Workshop scenarios break after reloading the world [1.203.6]

Upon loading a Visual Scripted scenario from the steam workshop, all works as expected. However, after saving and reloading the world, the scenario scripts stop running.

Steps to recreate:

1. Start a scenario you have subscribed to in the steam workshop. Note that it cannot be a KSH scenario, or one you have made yourself (see below).
2. Once the scenario world has finished loading, confirm that the scripts are working. This can be done either by waiting to see any events caused by the scripts, or using the 'Scripting tools' menu opened by pressing f11 twice (only available in offline games).
3. Save the world and exit to the main menu.
4. Reload the save. The scripts will no longer be running.
   

This does not effect KSH or self-made scenarios, as the game will incorrectly load the locally stored scripts, rather than the workshop-downloaded scripts. However, In most cases this will be unnoticeable (the local scripts may not be significantly different than what is on the workshop).

While testing the issue, I found that data in the SBC file for the scenario world, labeled 'LocalModPath', is changing as the scenario is saved and loaded. When viewed directly from the workshop download folder, the 'LocalModPath' usually lists a file path directing to the scenario creator's '...\AppData\Roaming\SpaceEngineers\Mods\' folder, where locally created scenarios are stored. After loading the scenario in game, 'LocalModPath' in the save file instead leads to the '...\steamapps\workshop\content\244850\' folder, where workshop downloads for SE are stored (as one would probably expect). The issue appears after loading the saved game; 'LocalModPath' disappears entirely from the SBC in the world save.

Included are videos of the bug occurring with:

• 'Example Scenario' by Chipstix213.
  
• 'Rogue Jump' by mglisson.
  
• 'Pyramid PVP Deathmatch Arena' by the.timothy.joseph

In every case, after reloading the world, the script is no longer shown to be running, and scripted buttons are unresponsive.

Also included are images of the relevant portion of the SBC file for 'Example Scenario', at various points in the saving/loading process.

1. 'Workshop' is how the file is when directly downloaded from the Steam Workshop (in the workshop\content directory).
2. 'Loaded' is from after loading the scenario in game, the saving and exiting the world (The SBC after it is copied to the players 'Saves' folder).
3. 'Reloaded' is from after reloading the above save file, and then saving and exiting a second time. As you can see, the 'LocalModFolder' entry is no longer present; the game has removed it.