Specific integer within an OPCarray

I have an array inside my OPC that I am currently pulling the entire array to my edge node and then to utilizing reference tags to get the data from the array.

How can I pull a specific integer from the array without utilizing the reference tags?

Example of my reference tag:

{
  "valueSource": "reference",
  "rawHigh": 100.0,
  "scaleMode": "Off",
  "opcItemPath": "[~]New Folder/Generator Modbus Array 2[6]",
  "dataType": "Float4",
  "sourceTagPath": "[~]New Folder/Generator Modbus Array 2[6]",
  "name": "Apparent Power",
  "tagType": "AtomicTag",
  "scaledHigh": 10.0,
  "opcServer": "PLC Next"
}

Example of my array tag:

{
  "valueSource": "opc",
  "opcItemPath": "nsu\u003dhttp://phoenixcontact.com/OpcUA/PLCnext/GlobalDataSpace/;s\u003dArp.Plc.Eclr/G250_Mapping1.G250_RegisterValue2",
  "dataType": "Int4Array",
  "name": "Generator Modbus Array 2",
  "tagType": "AtomicTag",
  "opcServer": "PLC Next"
}

I would like to get the integer at address 6 from the array, is that possible?

Does the server expose the array elements as their own tags?

Unfortunately it does not. I am not able to expose them as their own tag.

Utilizing OPC expert I can see the values inside the array however.

What's wrong with the reference tag approach?

The PLC is having issues with the large data pull. This is an operating system so I'm trying to avoid any online logic changes.

Reference tags aren't adding any load. You're already reading the whole array, at once as one tag. That's your only option if the server doesn't expose the elements as their own Nodes in the address space.

That's what I was afraid of.

I was hoping to not read the entire array and only the values necessary.

Unless the server supports some hidden syntax (like appending .0 or [0] to the end of the OPC Item Path (NodeId) I don't think you'll be able to.

Ideally you would have some control over how the data is modeled in the server and do something better than dump modbus registers into a large array, even if the elements are exposed.

When something is described as a "modbus array", I'd be inclined to try the modbus driver.