Your PC was a desktop system, the Mac is a laptop with the usual tradeoffs regarding performance.

For Mac there are tuning guides available that look similar to the windows tuning guides.

At the end of the day Windows and Mac are both non-realtime operating systems with the same challanges in terms of audio processing. Audio processes thus can not get a real-time priority to be processed guaranteed in time. Everything is built on certain programming conventions and there needs to be a certain balance. Low level routines (driver code) run as long on a cpu core until they detach themselve from it. The process schedulter may not interrupt that, thus any other process that was scheduled to run on that core needs to wait for its availability. This way also audio processes can be blocked. Therefore it's a good strategy to avoid a high interrupt / driver load on a system and to avoid accessing WLAN/LAN because this causes a lot of additional interrupts and low level routines that again can block the CPU core from processing audio in time. On Windows long lasting drivers result in a higher so called "DPC latency" which you can measure there with a tool called LatencyMon, you might know that already. The same things happen also on Mac, but could have different names, whether such tools exist on MacOS to be able to analyze it .. might be, but I don't know.

Audio projects also differ much in terms of performance / near-real time demands depending on the project structure.
In the one project the challenges can be CPU hungry VST/VSTi or if you are the kind of guy using many inserts in a track which requires a high single thread performance of your CPU, because all inserts usually run in one thread (I think because of performance reasons).

Finally there are also some differences in DAW, some have or had the habit to require a high single thread performance on the first CPU core which (from what I read) can be a limiting factor for DAW projects (Apple Logic). This information is years old, not sure whether it's up-to-date, I only wanted to put some examples.
How similar Windows and MacOS are from hardware perspective you can see, that with Intel CPU's it was possible to use the same HW for Windows or MacOS. You could built a Hackintosh or use Bootcamp to run Windows on Mac.

It's generally a good strategy:
- not to update MacOS to quickly, look for recommendation of the vendors whether the latest and greatest is supported
- maybe disable auto updates so that this is under your control
  ideal: allow notifications about security updates but deploy when you decide, only notification about major OS updates.
- to turn energy saving off as much as possible to prevent DPC latencies and throttling of CPU (challenging with a laptop)
- avoid a high interrupt load, so turn off WiFi, Bluetooth
- keep the amount of background processing low (auto updaters, network accesses, e.g. to cloud)
- do not access the network while you need full performance for audio
- try to connect the recording interface directly behind the USB controller
- disconnect all other USB devices, that you do not need (check whether it makes a difference or not)

- try whether it makes a difference to use USB3, although thunderbolt should be better (external PCIe)
- try all USB ports

If you have latest hardware with unequal CPU cores (performance, efficiency cores) then I could think of, that development of the process schedulter maybe needs more polishing, which interrupts or process load to put on which core. The more complex the hardware/cpu becomes the more intelligence and application recognition you need, maybe this also needs some further tuning. Audio processing is always a bit special because of the near-realtime requirements in processing.

Long story short, I would google for topics like mac and ( music production or audio), the google syntax for that is:
optimize mac for ( music production | audio )

Then you find links like that: https://www.sweetwater.com/sweetcare/ma … imization/