That's a killer - it's 2022 and Apple are still the only company who can get that right. I'd switch over to a Framework in an instant (for dual-boot Linux/Windows) if they could fix that.
AMD still supports S3 sleep on their Ryzen processors, but you'll need to check user feedback to make sure that the vendor did their job implementing it properly. In S3 sleep, the UEFI/BIOS is responsible for suspending and resuming hardware state. If not implemented correctly, you'll have high battery drain (components not suspended) or bugs on resume. Lenovo had dropped the ball on that front repeatedly, with the last two gens of T14 requiring BIOS updates to fix issues.
Wait what? How is that allowed?? What is the replacement?
Looks like they can get away with it ¯\_O_/¯
> What is the replacement?
S0ix sleep (named s2idle in Linux), where the OS is responsible for suspending / resuming all non-essential functions. Work is ongoing on the Kernel and drivers to improve it, but there is a long way to go (yay Monday mornings with an empty battery because the power draw is still > 1W).
Even Windows is unable to make it correctly work without killing the battery overnight, so they now default to hibernating to disk after a couple of hours. This strategy is also possible with Linux, but making it work alongside full disk encryption is tricky: https://wiki.archlinux.org/title/Dm-crypt/Swap_encryption#Wi...
There can be lots of EC/BIOS issues for suspending, IMO it's one of the best arguments for going for a Linux-first vendor (Tuxedo, System 76, Slimbook, etc), as you know that their top priority should be to get basic stuff working on Linux.
I bought a XPS end of 2019 and had a very bad experience forcing windows to use s3 mode. Actually I eventually stopped bothering with windows standby and let it suspend to ram now because 95% the time I use linux anyways and there s3 works fine.
I was several times greeted with a very hot notebook at the morning, because windows decided to boot up and do system updates during the night while the notebook was supposed to sleep.
It sounds like you might be using 'shallow' or 's2idle' (suspend to idle) sleep mode? You might need to write 'deep' to /sys/power/mem_sleep. (But don't listen to me, mine segfaults!)