ID 534802 - Opening a Tracker4, CameraTracker or some CaraVR node's Properties breaks Nuke script serialisation indentation for that Nuke session

Problem summary
Opening a Tracker4, CameraTracker or some CaraVR node's Properties breaks Nuke script serialisation indentation for that Nuke session
 
This seems to affect C_Tracker2_1,  C_CameraSolver2_1, C_Stitcher2_1, C_CameraIngest2_1
 
This doesn't happen with Tracker, Tracker3 or other Transform or CaraVR nodes.
 
Customer reported version
nuke.13.2v5
 
Customer reported platform
centos7
 
Steps to reproduce
 
1) Open Nuke

2) Create Grade node

3) Copy the Grade node and paste it into the Script Editor, notice the contents of the node have a space indentation

4) Create a Tracker4 node
 
5) Copy the Grade node again and paste it into the Script Editor, notice the contents of the node have no indentation
 

 
If you save the Nuke script, this also has no indentation
 
Expected behaviour
For Nuke Script serialisation to keep having indentation
 
Actual behaviour
After a Tracker4, CameraTracker or some CaraVR node's properties are opened in a Nuke session, Nuke no longer adds indentation when serialising nodes.
 
Workaround
Close Nuke, reopen the Nuke script, without opening Tracker4, CameraTracker or CaraVR nodes, then save/copy again, then indentation will then be added when serialising.
 
Reproduced by support
This bug has been reproduced in:
Nuke 14.0v2 - Windows 10, CentOS 7.9, macOS Monterey
Nuke 10.0v1 - Windows 10, CentOS 7.9
 
Earliest version tested
Nuke 10.0v1 - This issue appears to be in all tested versions of the product