Microsoft has released security updates (SUs) for vulnerabilities found in:
Exchange Server 2013
Exchange Server 2016
Exchange Server 2019
IMPORTANT: Updates are released in a self-extrac...
Updated Aug 11, 2022
Version 8.0
Blog Post
In our Environment (single on-prem Exchange 2013), enabling EP had no consequences on the public folders. No one is actually using them, but we have an old contact list in public folders, and it is still accessible despite having EP turned on. You could just try enabling EP and if public folders no longer work, try the fix shown at the end of the documentation or if nothing helps, just rollback EP (the script itself offers rolling back and creates a backup file before changing anything).
In my case (Exchange 2013) no reboot was required after August 2022 SU installation. However, I still rebooted just in case. Regarding Extendended Protection script, no reboots are required.
Have you done everything like described here?
https://docs.microsoft.com/en-us/Exchange/exchange-tls-configuration?view=exchserver-2019
Maybe also add: "SystemDefaultTlsVersions"=dword:00000001