I think there are two different scenarios here...
1) You have your own domain, and you want a catch-all for emails that are clearly intended for your domain but, lacking an accurate recipient, would otherwise be undelivered. Pretty much, as described by Weaver, it is common for mail hosting services to provide a way to catch these.
2) You use a public domain, such as gmail.com. In that case, Google seem to have taken it upon the themselves to offer a broadly comparable feature, albeit way outside of the smtp protocol standards. Trouble is, it is all very well for Google to say “We have had a great idea” and implement their own proprietary extensions to smtp but in reallity, they leave themselves open to attacks such as described by Broadstairs. And having set the precedent, and the illusion that it is useful, and 100s of millions of google users probably rely upon it, it would be very difficult to retract.
To be clear the problem I foresee is... a scammer sends an email designed to get attention, by asserting “your email address has been changed”. The recipient notices subtle changes (unexpected dots) and panics “Oh no, so it has”. In the panic, a malicious link gets clicked.
I know of no other mail service, other than gmail, that have taken it upon themselves to ignore dots. Remember, Google officially stopped “not being evil” some years ago now.