Can I Use DefaultMixedRealityProfile Instead of OpenXR Profile for MRTK2 on Meta Quest 3?

Question

I'm developing an application using MRTK2 for Meta Quest 3.
By default, MRTK2 provides the OpenXR profile, and I initially thought this was required for building on Quest 3. However, when I built my project using DefaultMixedRealityProfile, it still ran normally on Quest 3.

This made me wonder:

• Is it possible and valid to use DefaultMixedRealityProfile instead of OpenXR profile when customizing the MRTK2 profile for Quest 3?

• Are there any potential issues or limitations I might encounter if I use DefaultMixedRealityProfile instead of OpenXR profile?

I previously built a project using a different profile, and the behavior was strange, so I suspect I made a mistake. However, I want to confirm whether DefaultMixedRealityProfile is actually a valid option for Quest 3 development in MRTK2.

I'd appreciate any insights or clarifications on this. Thanks!