Do you not see the contradiction in your first acknowledging this:

And even though that class of vulnerabilities don't affect Perl,

And then going on to add this: it would be correct and a good practice to include it anyway, ?

In C and similar languages where that vulnerability exists, such advise is warranted and good practice.

But blindly transferring that to Perl is like trying to transfer the good practice of wearing seat belts in cars, to motorcycles. It simply doesn't work the same way.

I do not think that you pointing out that the extra care is unnecessary in this very case was very beneficial to the whole discussion.

Far better to know (and point out) when such practices are applicable -- which AnomalousMonk has more than demonstrated that he does -- than to blindly apply it when it is inapplicable.