This data allows you to get the current camera position as it moves through the cockpit.
This simvar is readable via coherent and SimVar.GetGameVarValue within javascript, and you can set L:vars to read via the gauge api. This workaround sacrifices a few frames and causes a noticeable lag when simulating collimation.
Having this simvar readable directly with simconnect will mitigate the lag.
Having it readable via the gauge api would be a bonus, but I don't think reading xyz structs via "execute_calculator_code" or "aircraft_varget" is possible, unless I'm mistaken.