You can disable SIP and even disable immutable kernel text, load arbitrary drivers, enable/disable any feature, remove any system daemon, use any restricted entitlements. The entire security model of macOS can be toggled off (csrutil from recoveryOS).

Aware of that. Way too big of a request just to make reasonable configuration changes, like shutting down daemons, etc.

No, it’s not that big a request. You literally have the capability. The average user does not need it.

What is hard about this?

Stopping/disabling a service should be a command, like it is on Windows or Linux. Not configured on a read-only volume bundled with other security guarantees.

It's pretty simple to keep these two things separate, like everywhere else in the present and history of the industry.

Just because Windows/Linux do things one way doesn't mean the rest of the industry has to follow it. ;P

Just out of curiosity, are these philosophical objections or do you have a practical use for disabling code signing and messing with your boot volume?

I have practical use for disabling telemetry and other misfeatures. (Maybe you meant to reply to your sibling comment?)

No, I meant to reply to you. I was curious about your practical use case for disabling code signing (which I think is what you refer to by telemetry) and messing with the boot volume.

Not what I am referring to. The goal is to disable misfeatures, not reduce security. Only Apple bundles the two.

He's a religious linux believer that will make you call him GNU/Linux believer - no point in argueing, there is not interest in the argument.