Onlyfun Asking just in case, cause there are a few vague warnings here and there that changing anything other than what is facing the user can 'break' the system's security, without any further details.
I think the short answer is that disabling or deleting any system component takes you outside the envelope of what has been tested. Since things in Android (for better or for worse) are interconnected in unpredictable ways, the results of leaving the envelope are unknowable, and negative results may turn up only weeks or months later, at which point it may be difficult to remember exactly what was deleted or disabled.
Personally I would not recommend disabling or deleting any system component without reading the source code for it, and also the code for anything that tries to call on it.
Onlyfun Or if you know some comprehensive but safe debloat list for gos that you've successfully tried, if there are any at all.
Most of what shows up on this forum about "debloating" is people asking why something is broken in a weird way and then finding out that something they "debloated" was actually necessary. It can be easy to imagine that one can tell from something's name everything it does, and sometimes that works out, but often not.