Entering Play mode takes ~0.5 seconds longer when com.unity.pipeline is installed

How to reproduce:

1. Create a new project
2. Copy the attached “PlayEntryProbeFinal.cs“ into the Assets folder
3. Enter Play mode, then exit Play mode
4. Repeat step 3 three more times
5. Observe the “Session summary by configuration“ section in the Console
6. Open the terminal
7. Navigate to your project in the terminal
8. Run: “unity pipe install“
9. Focus the Editor and let the package load
10. Run: “unity pipe list“ and ensure everything is connected
11. Enter Play mode, then exit Play mode
12. Repeat step 11 three more times
13. Observe the “Session summary by configuration“ section in the Console

Actual result: Entering Play mode takes about 0.5 seconds longer after installing com.unity.pipeline. The Editor freezes during startup, before the scene loads.
Expected result: Entering Play mode takes the same time before and after installing com.unity.pipeline.

Reproducible with: 0.7.0-exp.1 (6000.7.0b1)
Not reproducible with: 0.6.0-exp.1 (6000.7.0b1)

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

Notes:

• The attached tool keeps every Play mode entry of the current Editor session and groups them by configuration. To start a fresh set, use Tools > Play Entry Probe > Clear History, or close the Editor.
• The size of the delay varies between projects. Measured at ~0.5 s in one project and ~1.7 s in another on the same Editor version and package version.