AssetImportWorker crashes on RaiseException when switching to custom Meta Quest platform in Build Settings

Reproduction steps:
1. Create a new project (preferably using VR template, as it contains all the packages needed to create a Meta Quest Build Profile)
2. Navigate to Build Profiles (File → Build Profiles)
3. Add a new Meta Quest platform (click the "+" button at the top-left of the window to create a new Build Profile, select a platform under the "Platforms")
4. Switch to the new platform (select the newly created Build Profile from the left panel and click the “Switch Platform" button at the top of the right panel)
5. Observe the result in the console

Actual result: The AssetImportWorker crashes
Expected result: The AssetImportWorker does not crash after switching platform

Reproducible in: 6000.0.76f1, 6000.1.0a3, 6000.3.16f1, 6000.4.8f1, 6000.5.0b10, 6000.6.0a5
Not reproducible in: 6000.1.0a2

Reproducible on: Windows 11
Not reproducible on: No other environments tested

Notes:

• Couldn’t verify that regression happened between 6000.1.0a3-6000.1.0a2, but the last version where the issue could be reproduced was 6000.1.0a3. The issue suddenly stopped reproducing in 6000.1.0a3
• The issue reproduces once per project
• Sometimes the issue reproduces inconsistently, after switching to custom Meta Quest platform, try to switch to a default AndroidXR platform
• Similar issue but with different error reproduces in 6000.1.0a1 (Fatal Error! The file ‘MemoryStream’ is corrupted! Remove it and launch unity again!)
• The issue does not reproduce with custom Windows or Android profile
• Reproduces with Android XR and custom Android XR build profile as well

First few lines of the stack trace:

0x00007FF8FEED79DA (KERNELBASE) RaiseException
0x00007FFFD0504609 (Unity) EditorMonoConsole::LogToConsoleImplementation
0x00007FFFD05052F0 (Unity) EditorMonoConsole::LogToConsoleImplementation
0x00007FFFD118248D (Unity) DebugStringToFilePostprocessedStacktrace
0x00007FFFD1181809 (Unity) DebugStringToFile
0x00007FFFCF13D9B2 (Unity) GetManagerFromContext