Yeah, not everything needs to be coded like you're showing it off on github. Not that you can't do some nifty stuff, elegantly, in Perl.
Should you write your entire codebase in Perl, in 2018? hell no
But you probably shouldn't be writing anything more than 10-20 lines in Bash, either, and this class of organically evolving script, with little attention to design at the start (much like the language itself) is where Perl really shines.
s/guts to rewrite them/staff experienced in both languages, with access to the original requirements, and knowledge of said system, in addition to full support from management to swap out working code with fresh, potentially buggy replacements, instead of devoting time to other projects which may actually be profitable/g
As a sysadmin who started out replacing power supplies as a datacenter tech, and nowadays wrangles AWS auto-scaling groups, the idea of _not_ automating away the tedious parts of my job is pretty hilarious. I had one operations/support job where this was the case, and thankfully, I quit after one month.
If anyone out there has the gumption to cobble together a dev environment and automate away their BS job, yet can't get recognition from your employer; it is time to seek out a new job, you've certainly got the skills for something better!