In case you still want workflow visibility, a solution that will stop this from happening accidentally is to use windows "read-only" functionality.
If you right click on the workflow wherever it is saved and select "Properties" you can check off the "Read-only" Attribute.
Then, if you try to make a change and save the workflow, you will get the following error in Alteryx:
The advantage of this method is that you can pretty easily uncheck this option so that you can write your own copy, and if the end user wants to see what your code is doing, or see the workflow as it runs, they can do so. The disadvantage is that basically anyone with access to this file/folder can probably uncheck the Read-only box, so someone intentionally or deliberately saving the workflow will still be able to do so.
You could also get even more advanced (depending on how this folder is secured) and add/remove baseline Windows security permissions for the file, so that anyone other than you/admins can ONLY read the file, and cannot save/edit it.