ID 354032 - Large number of Denoise2 nodes in script slows UI even when script is cached.

Problem summary
Large number of Denoise2 nodes in script slows UI even when script is cached.

A large number of Denoise2 nodes in a script slows the UI/lags interaction, even when any knobs adjusted are not part of the script. 

Customer reported version
nuke.11.1v3

Customer reported platform
windows10

Steps to reproduce
1) Open Nuke.
2) Open attached script and reconnect the read node to an image.
3) View the bottom node to cache the script.
4) Deselect any selected nodes.
5) Press "g" to create a grade node.
Result: Grade node takes an abnormal amount of time to be created. Other functions experience a similar delay.

Workaround
Unknown.

Note: Issue does not seem to occur with an equivalent number of legacy Denoise nodes.

Reproduced by support
This bug has been reproduced in:
11.1v4 - Windows 10, Centos 7.4, OSX 10.13.2
11.1v1 - Windows 10
11.0v4 - Windows 10
11.0v1 - Windows 10, Centos 7.4, OSX 10.13.2

Earliest version tested
10.5v7 - Windows 10, Centos 7.4, OSX 10.13.2 - The problem does not occur in this version and has regressed.

Expected behaviour
UI and functions should not lag when all nodes are cached to memory and the script is not being recalculated.

Actual behaviour
The UI and other functions lag when a large number of Denoise2 nodes are in the script, even when that section of the script is not being altered and the nodes are cached.