Input Axes on some controllers not read correctly (Windows/Android)

I am writing a R/C flight sim on the Meta Quest and as such want to support R/C controllers hooked up to the Quest. I’ve noticed that some input axes are not read correctly. When I look at the StateBlock of the input device, I can see the position of axes in the raw data as I move the sticks. However when I query the offset of those axes based on the offsets given in the InputControl, some of them (in my case often “/rightStick/y”) are off by 8 bytes leading to nonsense results.

Given it’s on the Quest and without the USB port available it’s very difficult to debug, until I also found a R/C controller that gives a similar result on Windows. The controller is recognized correctly by Windows, and all axes work correctly:

However, in Unity the two sliders share the same offset in the StateBlock (128 bits), while one of them should be at 112 bits.
I’ve tried debugging the InputSystem, but it seems the issue is further down the system, because this is the capabilities JSON string for that input device presented to the InputSystem, already containing the incorrect offset:

I cannot find any reference to this issue, so any light that can be shed on this would be very much appreciated.