Several people mentioned in the forum that the only way at present to disable some of the services loaded by the Default Config is to disable everything and then manually enable only those you’re interested in.
And in many cases, you simply want to remove a single one (e.g., Remove only DHCP Discovery).
There is also an old, and seemingly archived, discussion on a proposal to fix that: Why the heck is default_config so difficult to customize?
However, after many years, there appears to be no real solution to this.
From the outside, it might seem that some people want to force you to load those services, by making it difficult and inconvenient to disable them, even though it has been proven that not all of them are necessary for the core functionalities of Home Assistant.
As noted by others in the forum, there are several disadvantages to this approach; for instance, it forces you to check the configuration file each time there is an update so that if a new service is added to the default, you can add it to your configuration as well.
I think it would be beneficial to have a way to simply disable a few default services that you are not interested in, as suggested in the archived post mentioned above.
However, I would suggest a more general approach: you could have an on/off flag for each service, allowing you to simply add a new line to the configuration file to decide whether to disable a specific one. That should be compatible with the current structure and shouldn’t require any changes to the default_config.
Does that make sense to you?
Thanks