We don’t have Wasabi in our integration guides despite it being fairly well known… and there must be a reason for that. I couldn’t connect to Bitcoin Core now, and I’d assume the lack of previous guides for Wasabi was because this has long been the case.
For the last few versions of macOS, there has been a new security feature where applications are blocked from accessing the local network. Wasabi does not appear in the list to assign permissions, which means it either isn’t currently set up to work properly, or it simply doesn’t even attempt to access the .local (if you use that – it to be honest, it seems to be configured by default to only access Core running on the same device).
Wasabi also has an option to run Tor inside the app, but that’s on another tab and seems rather specific to accessing this Wasabi API thing. Adding a .onion for Bitcoin Core doesn’t seem to work at all.