I think you are overlooking something. If I notice a random tramp.el in some unusual place, I will investigate it right away because I know .el files can be executed by emacs. I wouldn't do it for a random data file without extension or a compressed .gz archive unless they have executable permission for some unknown reason. Data files are created by many applications and it is concerning me as long as no program I frequently use will execute them randomly. You can say that data files should never be in the load-path of emacs and I will agree with you. However, I can see scenarios when this can happen unintentionally. It would be careless not to try to add a simple safeguard to prevent this kind of execution.
I did fix the proximal cause already, worked around this function and patched my emacs, so this bug doesn't affect me in any way now. Now I am trying hard to fix the root cause. This is why I reported this bug, shared my patches and addressed all valid concerns that were expressed here, even those that aren't that important for me personally. The most difficult part seems to be in persuading developers that this is an issue to be fixed. If I fail at this, I simply will be less confident in using emacs.