I understand the business context from which these survey questions are posed. Your intention is to increase regression effectiveness by ‘more bugs’ per suite, and reduce regression ‘waste’ by avoiding tests that won’t ‘yield’ ‘bugs’.
As you might have already observed in your experience, regression is not a ‘set’ set of ‘tests’ that you can execute and compare efficiencies. Software under development keeps evolving, and hence your regression ‘tests’ should keep pace with that too. More so with continuous integration and deployment. If you take that into consideration, every regression run could involve different set of test cases, which needs be intelligently selected and overseen by humans (I have to explicitly say that!)
I would say it would make sense to pick your regression ‘areas’ or ‘themes’ for a regression run (you can think of it as parallels to ‘modules’ in software code), and focus on those as you deemed fit. Of course, how large or how small your ‘area’ is is up to the context.
Finally, the survey sounds too ‘mechanical’, more inclined to a rigid environment of execution of regression ‘tests’, while software regression is far from it. It involves a lot of human ingenuity in thinking, observing, adapting, and orienting the ‘tests’.
Hope that helps. Feel free to message me to discuss your company’s regression situation if you need help and if you would like.