You need to help us to understand your work-flow.
>I set up a file system repository called "upload". My intention is to avoid making hundreds of copies of SCORM zip files which would cost me hundreds of GBs of disk space
What is the use case which warrants making hundreds of copies of files?
BTW, you know that if you upload the same file (in its content) hundred times to Moodle it takes up only one space, even if you keep on changing its name? So if you do the same manually, by uploading the file to a file system repository and linking it, you are not saving any storage space.
>I set up a file system repository called "upload". My intention is to avoid making hundreds of copies of SCORM zip files which would cost me hundreds of GBs of disk space
What is the use case which warrants making hundreds of copies of files?
BTW, you know that if you upload the same file (in its content) hundred times to Moodle it takes up only one space, even if you keep on changing its name? So if you do the same manually, by uploading the file to a file system repository and linking it, you are not saving any storage space.
> So, by uploading SCORM zips to one place, I can use the builtin Link
function of a SCORM activity to reference that one zip file.
The question is when should Moodle detect that a SCORM file has changed its content and show the new content. I don't know, I don't use SCORM. You need to ask in the SCORM forum.