It'd would be good if in the Step settings for LV modules we can have a button which can trigger the test saying is that module going to work when we change Development Environment (DE) to Run Time Engine (RTE).
Now, in case like this, we have only a dry information saying TS cannot load the module because probably VI is broken. Problem is, when we switch over to DE VI is NOT broken.
Of course the reason behind is that RTE has not enough information to call one of dependencies, or there is ambiguity in calling a sub-module - for example a dependent sub-module is used called by step earlier.
So, summarising, the test like that would be quite needed (saving time of development), and information returns shall be more detailed indicating the sub-module cannot be loaded by RTE and why.
I'm declining this idea due to lack of community support.
I'll also mention that there are other improvements in TestStand that should drastically help with this behavior:
1. 2017 and later do have much better error information (also requires LV 2018 or later)
https://zone.ni.com/reference/en-XX/help/370052AA-01/tshelp/infotopics/2017sp1whatsnew/#errorReporti...
2. The PPL Autoswitch feature in 2019 will let you switch from source VI's to PPLs at the adapter level, and PPLs should always run in the RTE:
https://zone.ni.com/reference/en-XX/help/370052AA-01/tshelp/infotopics/2019whatsnew/#PPL