nMeee AOSP launcher has a very focused and limited codebase comparatively with other launchers which is ideal for the system reducing attack surface and ease to bring it up for each Android version, release, patches etc.
Every feature or change made or provided for system based processes etc for UI changes and customisations adds to complexity, maintenance cost/debt, risk of exploitable bugs etc
For privacy and security keeping these things lean, well tested is best practice. When third party launchers can provide customisation for everything other than the settings UI and status bar icons has the least friction between development and user needs.
I used to be a magisk and xposed addict so I do appreciate where this feeling/sentiment comes from.
Previous post I made elsewhere:
appreciate the feedback, something to keep in mind though we're not an OEM with resources to focus on ensuring we have our own "skin" such as those found on OneUI, Nothing etc. also don't forget many of these companies prioritise aesthetics over security which is why you have access to patches months in advance on GraphenOS where they delay them up to 4 months. We're also the fastest other than Google to release QPR1 despite delays to AOSP and OEMs having early access. I'd rather those OEMs put their UI dept money toward their update and security dept instead.
Using the default AOSP Launcher also keeps code to a minimum with less complication in the system helping alleviate maintenance between updates as well as reduction in attack surface.