Our database query that searches the AE database for instances of hard coded literals throughout the system is so useful for general research, that I had it set up in our home-grown reporting tool so that all of the developers can run the query. It hits the database with a read-only service account, and they can toggle it between PROD and non-PROD.
As you said, the business concern is "what if" it hurts AE performance by adding unexpected load to the database. Yes all database queries cause load, and therefore run that risk. Because this risk is always greater than zero, all product vendors will advise you to not do it. In our case, I made the decision to accept the risk. I've been a SQL developer for over 20 years and sometimes just use my gut feeling. When I'm really concerned, I'll also run database explains against my SQL so I can evaluate its efficiency and consider tuning it for performance (serious tuning usually requires upgrades to the database itself, and I'll never do that to a vendor database!) But in this case I have never seen the query take more than a couple of seconds wall time to run, so I don't have any performance concerns.
I also run a monthly summary of task/workflow/aborts counts and throw them up in an Excel chart for management for trend analysis. I run this query from my developer SQL tool.