Same problem here.
I have a crashed thread of CoreSimulator’s loadValidCoreSimulatorService. Seems like the new Safari runs on a Catalyst-based simulator.
In my case, the termination reason from DYLD is a symbol not found in:
_launch_path_for_user_service_4coresim
from CoreSimulator, expected in /usr/lib/libSystem.8.dylib
Cleared all the cache and preferences, but it is likely to do nothing with simulator. Safe Boot still allows it to crash immediately.
Hope we won’t have all the ‘native’ apps run through a Catalyst for ARM versions, at least for this release. Looking for advices to fix the problem.