ID 371573 - Nuke will return a different hash after a script is saved, closed and reopened

Problem summary
Nuke will return a different hash after a script is saved, closed and reopened. This issue appears to affect the following nodes:
Roto, RotoPaint, GridWarp3, Assert, SplineWarp3, F_Align, F_ReGrain, F_RigRemoval, F_WireRemoval, ColorTransfer

Customer reported version
nuke.11.2v3

Customer reported platform
centos7

Steps to reproduce

1) Open Nuke.

2) Create a Roto node and attach it to the Viewer.

3) Open the Script Editor and run the following line of code:

 nuke.toNode("Roto1").opHashes()

Alternatively, you can also run the attached Python script (nuke_hash_bug.py) in the Script Editor, but you will need to change tmp_script (Line 5) so that it points to the hash_bug.nk script.

Reproduced by support
This bug has been reproduced in:
Nuke 11.2v4 - Windows 10 - macOS 10.14 (Mojave) - Linux CentOS 6

Nuke 11.2v1 - Windows 10

Nuke 11.1v6 - Windows 10

Nuke 11.1v6 - Windows 10

Nuke 11.0v4 - Windows 10

Nuke 11.0v1 - Windows 10

Nuke 10.5v7 - Windows 10

Nuke 10.5v1 - Windows 10

Nuke 10.0v6 - Windows 10

Nuke 10.0v1 - Windows 10

Nuke 9.0v9 - Windows 10

Nuke 9.0v1 - Windows 10

Nuke 8.0v7 - Windows 10

Nuke 8.0v1 - Windows 10

Nuke 7.0v10 - Windows 10 - macOS 10.14 (Mojave) - Linux CentOS 6

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

Expected behaviour
Nuke should return the same hash before and after the script has been saved, closed and reopened.

Actual behaviour
Nuke returns a different hash after a script is saved, closed and reopened.