Out of curiosity, do you need to keep your scripts as Perl scripts? If not, here's another approach that you can consider. Use something like pp from PAR::Packer to bundle your Perl script into a stand-along executable.

One advantage of that approach is that you don't have to manage Perl environments (versions of Perl installed, which modules are installed, which versions of modules installed, etc.) on multiple systems. Instead, you just manage your development Perl environment and distribute stand-alone executable files. Of course, one drawback is end users will not be able to modify the code as easily (which could be a good thing in certain situations).

If you still need/want to keep your scripts as Perl scripts, there's two other approaches that you can consider. You can use App::FatPacker to "pack your dependencies onto your script file", but I don't think that it will work for XS based modules.

If all of the systems have access to a file server, you can put a Perl installation (such as portable Strawberry Perl) on the file server. The other systems then can map a drive to the file server and use that Perl installation.

Just tossing out some ideas about alternative approaches.