Desktop Safari doesn't have a cellular baseband to worry about. Even the wake-briefly-from-sleep-to-check-email feature in macOS is only activated when the Mac is on a wired or previously joined WiFi network. It doesn't randomly blast signals in your backpack on the subway trying to check e-mail and notifications draining the battery. There's also not the same jetsam policy on macOS since it does support swap.
Batteries have finite power density and an iPhone has a finite volume for a battery. So there's only so many watt/hours that can fit into an iPhone. Unrestricted background network/processing means much reduced battery life. That's a bad thing for a phone. It's doubly bad for a device that's a device that's also an electronic wallet and navigation aid.
Smartphones aren't laptops and neither phones or laptops are desktop systems constantly plugged into mains power. A system that makes sense for a desktop on mains power plugged into Ethernet with 32GB of RAM and essentially unlimited swap does not necessarily make sense on a battery powered device with only radios for connectivity and a fraction of the RAM and no swap.
But I get it, Apple Bad and everything they do is a vast conspiracy.
A lot of the Chrome team's "standards" have problems with accessibility, workability on mobile, security[0], privacy[1], or just battery life. Some are neat experiments that are or only will be used in the wild by advertisers to track and identify users.
Because the Safari/WebKit team doesn't have to chase users for revenue like Mozilla does they can afford to be more conservative with what Google "standards" they support. Being able to offer a tighter privacy posture or efficiency is part of the iOS/macOS sales pitch.
[0] https://github.com/WICG/webusb/issues/50
[1] https://www.theverge.com/2021/4/16/22387492/google-floc-ad-t...