Really? Do you have any stats/research that backs up that assertion? I'm not an expert on what developers do but I have extensive experience as a DBA and managing groups of DBA's and I have to say that we spent very little time re-working our modeling techniques. We had standard tools and techniques. We used them. Once in a blue moon we re-examined our methods agains the latest and greatest tools and techniques and adjusted as necessary.
I'm not sure what 'reinventing database access' means. We had some utility programs that generated CRUD code for tables and/or views if we needed it, but that was a very small portion of the work done by the DBA staff.
We did have standards about how the DBMS was used. We had those standards because often we had little control over how the development groups wrote their applications. We opted to put the business logic near the data to help ensure consistency across the application portfolio. It worked.
So, from my perspective, you're solving a problem that may not really exist on the database side.
RAP does not really address the problems of DBAs, whose primary job is to maintain existing applications. RAP is about new application development, where someone has to decide exactly how to do all the things that the article lists. I assure you, from many many years of application development experience, that these are the things that consume most of new application developers' time.