ID 360646 - The TimeWarp Soft Effect does not render all necessary frames when Exporting if Retimes are not applied

Problem summary:
The TimeWarp Soft Effect does not render all necessary frames when Exporting if Retimes are not applied

Customer reported version:
Nuke Studio 11.2v2

Customer reported platform:
Windows 10

Steps to reproduce:
1) Launch Nuke Studio/Hiero and add a 100 frame video clip to the Timeline.

2) Trim the clip to 50 frames, and add a TimeWarp Soft Effect to the clip (Right-click > Effects > TimeWarp)

3) Double-click the TimeWarp to view its Properties.

4) At Frame 0, set a keyframe for the input frame knob as: "0"

5) Scrub the Timeline to frame 50, and set the input frame knob to "99". The clip is now re-timed to 200%.

6) Right-click the sequence and select Export (or press Ctrl+Shift+E).

7) Render an EXR sequence using "Process as Shots" while having "Apply Retimes" unchecked.

8) Observe how only 50 frames are rendered.

Expected behavior:
All frames needed to recreate the TimeWarp soft effect should be rendered if "Apply Retimes" is not enabled.

Actual behavior:
When a Clip has been retimed with a TimeWarp, if "Apply Retimes" and/or "Include Effects" have been disabled the Clip will be exported based on its Destination Duration instead of its Source Duration. 

If the Clip has been retimed to with an Editorial Retime (Right-click > Editorial > Retime...) instead of a TimeWarp, then the original 100 frames will be exported if "Apply Retimes" is unchecked.  

Workaround:
1. When exporting the shot, ensure the "Keep Nuke script" knob is enabled.

2. When the shot becomes exported, open the Project Settings of the Nuke script that was saved by the export.

3. Change the duration of the clip and re-render the shot.

Reproduced by Support in:
Nuke Studio 11.2v3 - Windows 10, CentOS7, macOS 10.13

Nuke Studio 11.2v2 - Windows 10, CentOS7, macOS 10.13

Nuke Studio 11.2v1 - Windows 10, CentOS7, macOS10.13

Nuke Studio 11.1v5 - Windows 10, CentOS7, macOS 10.13

Nuke Studio 11.1v1 - Windows 10, CentOS7, macOS 10.13

Nuke Studio 11.0v4 - Windows 10, CentOS7, macOS10.13

Nuke Studio 11.0v1 - Windows 10, CentOS7, macOS 10.13

Nuke Studio 10.5v7 - Windows 10, CentOS7, macOS 10.13

Nuke Studio 10.5v1 - Windows 10, CentOS7, macOS 10.13

Nuke Studio 10.0v6 - Windows 10, CentOS7, macOS 10.13

Nuke Studio 10.0v1 - Windows 10, CentOS7, macOS 10.13

Nuke Studio 9.0v9 - Windows 10, CentOS7, macOS 10.13

Nuke Studio 9.0v1 - Windows 10, CentOS7, macOS 10.13

Earliest version tested:
Nuke Studio 9.0v1 - This issue appears to be in all versions of the product.