I've definitely done what you describe of just having my SAM monitors call local files. As you said its kludgy but does the job. The usual problem I run into here is that server admins write scripts for the purposes of things they need done, and almost never care to think about the format requirements I have in order for SW to interpret the results of their scripts or to collect monitoring-centric metrics in their scripts.
For me, when working in places with good script source control like a Git I have built automations where the latest version of the scripts is just inserted directly into the SAM DB. Not sure how into the weeds you want to go with it, but all the necessary verbs do exist where you could automate the whole process of creating scripts in the repository, have that kick off a script that goes into SAM and creates a corresponding powershell component monitor with the script body being set from what's in your repo, or updating the existing component to reflect any script changes. Within 1-2 polling cycles all the new version of the script will be in effect.
Getting it all to work requires a pretty strong understanding of the Orion API verbs and the SQL table relationships unfortunately, but it can be done.
