ID 480324 - Errored Text2 nodes are evaluated while not connected in command line mode.

Problem summary
Errored Text2 nodes are evaluated while not connected in command line mode.

Customer reported version
nuke.11.3v6

Customer reported platform
windows10

Steps to reproduce
*Requires a font to be un/installed on the machine.
1) Ensure a specific font is available, then launch Nuke.
2) Create a Text2 node, and select the recently installed font, adding text to the message box.
3) Create a Checkerboard and Write node detached from the Text2 node.

​​
4) Save the script and close Nuke , then remove the font from the system.
5) Open a command prompt/terminal window.
6) Path to Nuke, then render from the command line with the  Nuke13.0.exe -xi -F 1-10 "path/to/nuke/script.nk" command.

Expected behavior
The disconnected node should not be evaluated or trigger an error when opening the comp in terminal. The render should complete without stopping from an error. The --cont flag is also not allowing the render to complete.

Actual behavior
The render fails because of the font missing error. "ERROR: Text1.font: Font (specificfontname.ext:0) not available."
​

​

Workaround
There is no available workaround at this time.

Reproduced by Support in:
Nuke 13.0v2 - Windows 10, macOS 10.14
Nuke 13.0v1 - Windows 10
Nuke 12.0v1 - Windows 10
Nuke 11.0v1 - Windows 10
Nuke 10.0v1 - Windows 10
Nuke 9.0v1 - Windows 10
Nuke 8.0v1 - Windows 10, macOS 10.14

Earliest version tested
Nuke 8.0v1 - This issue appears to be in all versions of the product