Many of your "best practices", as pointed out by others, are simply style guides. Hack out a Perl::Tidy configuration the team is happy with and most of that stuff is taken care of. Oh, you might still want to impose local constraints on identifier construction and stuff of that nature, but those really are not Best Practice items.

You may also find Perl::Critic is a helpful tool.

BTW: I find statement modifiers read very nicely. They break the flow much less than the same statement broken into two parts by forcing half of it into a block. A single succinct entity is easier to comprehend than the same code broken into two disparate parts.