All modeling is data. Dynamo can manipulate data more effectively and quickly than anyone can via point and click processes. Ergo at a certain point anything can be done via Dynamo which is within the limits of the API (something which is very robust). So when asked my response is usually something like Well, basically anything you would like to, after all everything in that rvt file is all just data, and Dynamo works well with data. What would you like to do with it?
Also, I wouldn’t sell “modeling“ work short like that - it is short sighted and dismissive of what a lot of people do. Design is the act of making and recording decisions in a way which will allow someone else to build the end result, nothing more. There is an art in how this is done for any trade or task, be it building massing, envelope design, fire alarm locations, or the rest. Any given trade has a different set of standards, guidelines, restrictions, and codes which vary by location (steel is different in Sweden from that in the USA), but even in the most prescriptive trades the decisions still have to be made and recorded to communicate intent.
For example, the task of “placing hangers equally” which you qualified as ‘modeling’ is a design task (well unless you are purely matching the field condition, in which case the hangers won’t be equally spaced and may not even be code compliant) in that the user has to decide if they really want to be equal with the guideline spacing even though hangers will interfere with ductwork, or leave more bulky hangers exposed in the area of open ceiling, or whatever else may come along as a reason to decide to start the pattern here, or use a beefier hanger there, or the like. And oddly enough the logic in the hanger placement tool could likely be tweaked and repurposed for tasks which are seemingly unrelated, say the design of the layout for horse stalls in a barn (something I have gotten to learn a little bit about in the last year).