ID 568092 - The Merge node becomes disconnected when upstream from a FrameHold, FrameRange, or TimeOffset node connected to a 3d node

Problem summary
The Merge node becomes disconnected when upstream from a FrameHold, FrameRange, or TimeOffset node connected to a 3d node.
 
Customer reported version
Nuke 15.0v1
 
Customer reported platform
Rhel 9
 
Steps to reproduce
1) In Nuke, create a 3d node such as a Sphere or Card.
2) Create a Merge node, then a FrameHold, FrameRange, or TimeOffset node and place it upstream into Pipe A or B.
3) Connect the 3d node upstream of the FrameHold/FrameRange/TimeOffset node.
4) Save and close the script.
5) Reopen the saved script and observe the Merge node input.

 
Expected behaviour
The Framehold, FrameRange, or TimeOffset node should remain connected to the Merge node.
 
Actual behaviour
The Framehold, FrameRange, or TimeOffset node becomes disconnected from the Merge node input.
 
Workaround
Adding a ScanlineRender or RayRender node between the 3d node allows the Merge node to stay connected.
 
Reproduced by Support in:
Nuke 15.0v4 - Windows 10, macOS 13 Ventura
Nuke 12.0v1 - Windows 10, macOS 13 Ventura
 
Earliest version tested
Nuke 12.0v1- This issue appears to be in all tested versions of the product