Report is here, GOOD NEWS. We can have author-controlled TF2M-only no-action-by-staff* crit choice. I actually went to test a different idea than I am posting, but as I was writing it out I realized a flaw in the method and so I am posting a similar but better solution.
*(required once, not every map an author wants changed)
Step 1: Our server config (which is ran every mapchange) is modified to include tf_weapon_criticals 1.
Step 2: A config named tf2mnocrits.cfg is placed on our server. It contains tf_weapon_criticals 0.
Step 3: Any author who wishes for crits to be turn off during testing on our servers needs only to use a logic_auto OnMapSpawn to tell a point_servercommand to exec tf2mnocrits and then the config that turns them off will be ran when their map runs.
This way people who want crits off can easily do so but have to make the effort themselves, and don't need to bug nor rely on any staff or test hosts remembering or having the ability to do it.
*(required once, not every map an author wants changed)
Step 1: Our server config (which is ran every mapchange) is modified to include tf_weapon_criticals 1.
Step 2: A config named tf2mnocrits.cfg is placed on our server. It contains tf_weapon_criticals 0.
Step 3: Any author who wishes for crits to be turn off during testing on our servers needs only to use a logic_auto OnMapSpawn to tell a point_servercommand to exec tf2mnocrits and then the config that turns them off will be ran when their map runs.
This way people who want crits off can easily do so but have to make the effort themselves, and don't need to bug nor rely on any staff or test hosts remembering or having the ability to do it.