ID 329780 - Frame Server - rendered frames will have the same creation date as the Nuke script

Problem summary
When rendering with the Frame Server, there is a bug where the rendered frames will have the same created date as the original Nuke script.

This appears to happen when a Nuke file is opened, and immediately rendered.  (No changes to the scene)

If something is edited in the project, or the project is re-saved, the rendered frames will have the correct time.  

Customer reported version
nuke.11.1v1

Customer reported platform
10.13

Steps to reproduce

1) Create a scene (Checkerboard -> Grade -> Write)

2) Setup the Write node's render location.

3) Save the project and close Nuke.

4) Wait a few minutes.

5) Re-Open Nuke.

6) Render the Write node with the Frame Server active

Result:  The rendered images will have the same creation date as the Nuke script 

Workaround
Any changes in the Nuke scene will reset the timer to the correct time.

For example:

1. Attach a Grain node
2. Delete the Grain node
3. Render

Disabling a node and re-enabling it will fix the render time.

Reproduced by support
This bug has been reproduced in:
Nuke11.1v1 - Windows 7 -Mac10.13 - CentOS6.9
Nuke11.0v3 - Windows 7 -Mac10.13 - CentOS6.9
Nuke11.0v1 - Windows 7 -Mac10.13 - CentOS6.9

Earliest version tested
- Nuke11.0v1 - This feature did not exist before this version

Expected behaviour
Rendered frames should always use the system's date as its creation date.

Actual behaviour
Rendered frames are being rendered with the Nuke scripts creation date.