That's not really a concern, I mean systemd is by far the most popular init system, and especially in a situation/environment where one might choose to run PowerShell it's highly unlikely that you'd be running any other init. Like if you're the kind who'd prefer dinit or S6 or something, you wouldn't even consider running a "bloated" shell like PowerShell in the first palace.
So there's no need to add a disclaimer. Microsoft can just deal with it the same way they deal with distro support - they officialy support Ubuntu but for others you're on your own, although they do provide tar.gz packages.
And yes, systemd is indeed quite complex but there's no reason it can't be translated across to PowerShell lingo, at least parts that makes sense.
Eg:
Get-Service -Name <svc> -> systemctl status <svc>
Start-Service -Name <svc> -> systemctl start <svc>
Stop-Service -Name <svc> -> systemctl stop <svc>
Set-Service <svc> -StartupType Disabled -> systemctl mask <svc>
And so on.They've had six+ years to do perfect this, which is plenty of time - if they were really serious in pitching PowerShell as a true cross-platform shell. But it seems like they don't really care, especially now that they've captured most Linux users by means of WSL2, so it makes more sense for them to invest in that rather than invest in cross-platform parity in PowerShell.