WP Health shows numerous performance issues precisely after “Optimizing” WAF

My newly installed WF WAF finally came out of learning mode, so I let WAF turn on “Extended Protection Mode.” Immediately afterwards, the WP Site Health started throwing a series of performance related warnings, which I expect are all related to the changes that WF WAF put into my .htaccess file.

The specific WP Health warnings are as below.
My thinking is the first two are caused by the third one, which is an inability to perform a loopback request.

3 critical issues

An active PHP session was detected
Performance
A PHP session was created by a session_start() function call. This interferes with REST API and loopback requests. The session should be closed by session_write_close() before making any HTTP requests.

The REST API encountered an error
Performance
The REST API is one way WordPress, and other applications, communicate with the server. One example is the block editor screen, which relies on this to display, and save, your posts and pages.

The REST API request failed due to an error.
Error: cURL error 28: Operation timed out after 10001 milliseconds with 0 bytes received (http_request_failed)

Your site could not complete a loopback request
Performance
Loopback requests are used to run scheduled events, and are also used by the built-in editors for themes and plugins to verify code stability.

The loopback request to your site failed, this means features relying on them are not currently working as expected.
Error: cURL error 28: Operation timed out after 10000 milliseconds with 0 bytes received (http_request_failed)