Your comments

The use of domains and sets of attributes goes a long way towards minimizing the amount of effort involved in creating a model. "Enterprise Class" modeling tools I have used over the past two decades typically do this as core capability. Specific example is the inclusion of audit fields in a table structure. They tend to be the same fields/types each time and would be nice to simply include them via reference instead of having to manually add them each time. When you have hundreds of tables in your model that can become quite a burden.

Completely agree! A lot of time is lost as a data modeler in making all tables and relationships legible. This is a must have capability in my opinion.