ID 580634 - Cloned TimeOffset nodes do not produce the same result as the original node

Problem summary
Cloned TimeOffset nodes do not produce the same result as the original node.
 
Customer reported version
N/A
 
Customer reported platform
Windows 11
 
Steps to reproduce
 
1) Open Nuke.
 
2) Read in some footage.
 
3) Create a TimeOffset node and connect it downstream of your Read node.
 
4) Check the reverse input knob. You should see that the Read node's footage will now be played backwards.
 
5) Clone the TimeOffset node (Alt+K) and connect the clone to the Read node as well.
 
6) Compare the results of each TimeOffset in the Viewer.
 
Expected behaviour
Cloned nodes should always produce the same result.
 
Actual behaviour
Any changes made to the original TimeOffset nodes are not reflected in the cloned node. 
 
Workaround
Unknown.
 
Reproduced by support
This bug has been reproduced in:
Nuke 15.1v1 - Windows 11 - macOS 12 (Monterey) - REGRESSION
 
Unable to reproduce bug in:
Nuke 15.0v4 - Windows 11 - macOS 12 (Monterey)
 
Earliest version tested
Nuke 15.0v4
- This issue doesn't appear in this version and has regressed