ID 353418 - Transcode Images and Copy Exporter do not set custom colorspaces when they are added as Read nodes to a Nuke Project File (exported Nuke script)

Problem summary
Transcode Images and Copy Exporter do not set custom colorspaces when they are added as Read nodes to a Nuke Project File (exported Nuke script)

Customer reported version
nuke.11.1v2

Customer reported platform
windows10

Steps to reproduce

1) Open Nuke Studio

2) Import a dpx image sequence and add it to the timeline

3) Right Click the clip> Set Media Color Transform > AlexaV3LogC

4) Right Click the clip> Export > Process as Shot

5) Export using the attached shot export preset

6) Open the Nuke script generated

7) Check the Read nodes, the ones created from the Transcode Images and Copy Exporter do not have the AlexaV3LogC colorspace set in their read nodes

If you disable adding the copy exported and Transcode Images to the Nuke project, then the Read node from the source file has the correct colorspace 

Reproduced by support
This bug has been reproduced in:
Nuke Studio 11.1v4 - Windows 10 - CentOS 6.8 - MacOSX 10.13
Nuke Studio 11.1v1 - Windows 10
Nuke Studio 11.0v4 - Windows 10
Nuke Studio 11.0v1 - Windows 10
Nuke Studio 10.5v7 - Windows 10
Nuke Studio 10.5v1 - Windows 10
Nuke Studio 10.0v6 - Windows 10
Nuke Studio 10.0v1 - Windows 10
Nuke Studio 9.0v9 - Windows 10
Nuke Studio 9.0v1 - Windows 10
Hiero 1.8v1 - Windows 10 - CentOS 6.8 - MacOSX 10.13

Earliest version tested
Hiero 1.8v1 - This issue appears to be in all versions of the product
- This feature did not exist before this version

Expected behaviour
For the Read nodes in the nuke script to have the correct colorspace

Actual behaviour
The read nodes have different colorspaces, such as Cineon or sRGB