I have already mentioned the issue of keeping non-used presets here : Performance issues - Helpdesk / SEO and Website Performance - Sitejet Community.
Well, @Andre you can say that this is not a big deal. But from the point of view of clean code, in my humble opinion, this is an issue. You may tell that this is not a priority, but I think it should be handled sooner or later by cleaning code before generating the production version of the website.
Clients are not all the same, and they can be picky on this subject, and Google Speed Insight output. And they are very aware, especially with all the Core Web Vitals communication and articles out there on the web. So, it is better not losing them by delivering a clean version of the site. I’m sure there is a way to do it automatically.
Just imagine, in case I test all presets on a website and then keeping only a few, the amount of non-used code we deliver. From a developer point of view, I don’t like it, as it is not optimal.