ID 557083 - Bounding Box knobs named "bbox" do not resolve correctly when expression linked with child parameters

Problem summary:
Bounding Box knobs named "bbox" do not resolve correctly when expression linked with child parameters
 
Other knob names, such as "BBox", "bbox_a", "box", or "foo", do not appear to be affected.
 
Customer reported version:
Nuke N/A
 
Customer reported platform:
N/A
 
Steps to reproduce:
1) Launch Nuke and create a NoOp node in the Node Graph.
2) In the NoOp's Properties, right-click and select Manage User Knobs...
3) Add a Bounding Box Knob named "bbox", then set the knob to values of your choice:
 

4) Create another NoOp node, and add a Bounding Box Knob named "test".
5) Open the test knob's Animation menu and select Edit Expressions...
6) Link the test knob to the bbox knob with expressions that use child parameter names, such as NoOp1.bbox.x, NoOp1.bbox.y, etc.
7) Observe how the resulting test values are always [0,0,1,1], and do not match their counterparts:  

 
Expected behavior:
Expression linked knobs should return the same value as the knob they are linked to.
 
Actual behavior:
Attempting to use child parameter names to access a Bounding Box knob named "bbox" will result in [0,0,1,1] instead of the correct values. 
 
Workaround:
Instead of referencing the child parameters (.x, .y, etc.), only using the knob name (bbox) seems to create the expected result:

 
Reproduced by Support in:
Nuke 15.0v1 - Windows 10, macOS 13 Ventura
Nuke 14.1v1 - Windows 10, CentOS 7
Nuke 14.0v1 - Windows 10
Nuke 13.0v1 - Windows 10
Nuke 12.0v1 - Windows 10
Nuke 11.0v1 - Windows 10
Nuke 10.0v1 - Windows 10, CentOS 7
 
Earliest version tested:
Nuke 10.0v1 - This issue appears to be in all tested versions of the product