Most FrameTiming metrics display 0 on Meta Quest 2/3

Steps to reproduce:
1. Download the attached user's project "BugRepro.zip"
2. Go to File > Build Settings... and switch to the Android build target
3. With a Quest 2/3 connected, select the Development Build option and then Build and Run the project on the headset
4. Open the Android Logcat Window in the Unity Editor and observe the Frame Timings being printed in the log

Expected Results: All frame timing metrics display non-zero values
Actual Results: All metrics apart from cpuFrameTime, cpuMainThreadFrameTime and framestartTimestamp display 0

Reproducible on: 2022.3.39f1, 6000.0.12f1
Could not test on 2021.3.39f1 due to project errors after downgrading

Reproducible with these devices:
VLNQA00609, Oculus Quest 3 (Quest 3), Android 12, CPU: Snapdragon XR2 Gen 2 (SM8550), GPU: Adreno (TM) 740
VLNQA00415 - Oculus Quest 2 (Quest 2), CPU: Snapdragon XR2, GPU: Adreno 650, OS: 12

Not reproducible on these devices:
VLNQA00422 - Galaxy S21 Ultra 5G (SM-G998B), CPU: Exynos 2100, GPU: Mali-G78, OS: 11
VLNQA00528 - HMD Global Nokia G20 (Nokia G20), CPU: Mediatek MT6765G Helio G35 (12 nm), GPU: PowerVR Rogue GE8320, OS: 13
VLNQA00423 - Google Pixel 3 (Pixel 3), CPU: Snapdragon 845, GPU: Adreno 630, OS: 9
VLNQA00381 - Xiaomi Redmi Note 8 Pro (Redmi Note 8 Pro), CPU: MediaTek Helios G90T MT6785T, GPU: Mali-G76 MC4, OS: 9
VLNQA00282 - Samsung Galaxy S10e USA (SM-G970U), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 9

Testing Environment: Windows 11
Not reproducible on: No other environment tested

Notes:
-Issue is not reproducible on standard android devices
-Issue reproduces with both OculusXR and OpenXR Plugins
-Log information:
cpuFrameTime: OK
cpuMainThreadFrameTime: OK
cpuMainThreadPresentWaitTime: zeros
cpuRenderThreadFrameTime: zeros
cpuTimeFrameComplete: zeros
cpuTimePresentCalled: zeros
firstSubmitTime: zeros
framestartTimestamp: OK
gpuFrameTime: zeros