Users don't care whether it is a bug or a "technical limitation" or whatever else, and rightfully so.
The expectation of a messaging app user is that message notifications arrive in a timely manner. This is straight up one of the primary features of any messaging app. If a messaging app cannot even do that, it is a no-go, full stop.
The whole "privacy issues" and "business model" talk is not something an average user cares about. They want their messaging experience to work smoothly and all primary features of messaging (such as notification delivery) to work in a way where they don't have to think about them at all.
RCS is normalised, and works at the same reliability as SMS for the vast majority of the global messaging community.
Not at all, no. Among my non-technical acquaintances they all (all, not just some subset) complain that RCS is unreliable seemingly at random some small fraction of the time. However it works most of the time and (unlike SMS) you can send high resolution pictures and (in particular) videos so they continue to complain about it rather than switching. (There are various downsides to any of the options they could switch to.)
An unspecified lack of privacy on an E2E app feels less palpable and not a blocker for a lot of people.
If you're hosting your own foss stack you get to take ownership of every gremlin - for better or worse - each problem becomes something you should be able to fix.