I built the tools for the way we work, Stack overflow built dapper for the way they work. Entity framework is out there and no one would dispute the usefulness of it for certain things.
As a developer you are free to choose your tools and hopefully you choose the tools that are most appropriate for the way you work. And I am providing another option, nothing more.
Primary advantages for EzAdo.
1) The procedures are prebuilt from queries around system objects, and all the parameter definitions are based off what the database (source of truth) knows.
2) You can load the parameters directly from an object, directly from Json, or set them by hand the flexibility is there. You can write objects if you want, but you don't really have to. That means you never miss a mapping.
3) If you have the REST stuff set up, as soon as you write the procedure the endpoint is exposed, there is nothing else to write and that is why we use it and the greatest benefit for us. Tuning an endpoint means tweaking a procedure.