Is it feasible to a) have the script rely on its own set of required modules or b) rely on it's own perl installation?

Many times I've had to ensure that a perl script will run even on machines where there is no perl installation. (I say "script" but really we're talking about an application suite here). So I compiled versions of perl for every known target OS and architecture and relied on a <ugh> sh wrapper for launch via a soft link.

That last is a lot of effort, generally not worth it for a single script. However if your machines share any file systems, it's worth considering perl from a depot.

I think I'd hone in on a core set of modules. For any that are "absent must-have's" then distribute your own version of the module along with the script.

Just remember that a little Perl is far better than no Perl.

Matt