I speak highly of htmx, but it isn't a "replacement" for anything; I see it more as something that is intended for a specific class of applications. Probably best for thin-client applications, that allow more than just navigating using hyperlinks, and sending form data over POST requests.
If a team is using htmx, I find that the team should be responsible to make it clear that the web application is more a thin-client application that provides a UX that is very similar to paper forms.
If stakeholders want more, it's time to transition away from htmx and onto something else, IMO