I wasn't concerned with this being an issue until I went to try to set up Rules to replace alerts on a list I had migrated over from On-Prem SharePoint to SharePoint Online.
Many of the lists we have migrated over in the past are not compatible with Rules (old templates don't allow for Rules) so that simplified option isn't going to be available for those users. Recreating the lists from scratch, and applying the Rules, it requires too many separate Rulesets to make this a viable solution, and even then, the options available only send links to the item, without providing any of the details in the email. Completely unacceptable.
Ok, so PowerAutomate then. Average users will not be able to utilize this... sorry, I am sure Microsoft was hoping that CoPilot would be at the point now that it could basically do the whole thing for users, but no, that is not the case. It's not even just the issue of working with the provided templates; its the Service Connectors. It's the shared ownership on Flows. Its email targeting (not working for SharePoint Groups, only for individual users / distro lists). Its the succession planning for flows, the proper apportionment, creation and maintenance of service accounts.
Sites and lists outlive users. When a user leaves, the rows and columns they created and populated in a list don't just go away. Reporting and alerts on these lists and document libraries should ALSO outlive the user. This is a major design flaw, and one that is going to cause massive headaches down the line with the way the alert structure is being replaced.