ID 377848 - Using nuke.nodes.Read() with high/large frame numbers takes longer to create Read nodes

Problem summary
Using nuke.nodes.Read() with high/large frame numbers take longer to create Read nodes, the higher the frame number, the longer it takes, even if the frame range for the sequence is exactly the same.

Customer reported version
nuke.11.3v1

Customer reported platform
windows10

Steps to reproduce

1) Download the attached frames

2) Open Nuke

3) Run the below commands, changing the <path> for the download path of the frames

nuke.nodes.Read(file="<path>/manyFrame.#######.jpg", first=1, last=2)

nuke.createNode("Read", 'file "<path>/manyFrame.#######.jpg" first 1000001 last 1000002', False)

nuke.nodes.Read(file="<path>/manyFrame.#######.jpg", first=1000001, last=1000002)

Result: The first two commands will create Read nodes almost instantly, the last command causes to to hang for a few seconds before reating the Read node

Workaround
Use nuke.createNode("Read") rather than nuke.nodes.Read()

Reproduced by support

This bug has been reproduced in:
Nuke 11.3v1 - Windows 10 - CentOS 6.9 - MacOSX 10.13

Nuke 11.2v1 - Windows 10

Nuke 11.1v1 - Windows 10 - CentOS 6.9 - MacOSX 10.13 - regression

Unable to reproduce bug in:

Nuke 11.0v4 - Windows 10 - CentOS 6.9 - MacOSX 10.13

Earliest version tested
Nuke 11.0v4 - This issue no longer appears in this version and has regressed

Expected behaviour
For Nuke to create the Read node almost instantly when running nuke.nodes.Read() with high frame numbers

Actual behaviour
Nuke hangs and takes longer than it should. The higher the frame number, the longer it takes.