I certainly don't consider it a complete method for handling all cases, but modification of large groups of modules tends to go like this. Run some wide scans, fix the obvious cases, and then work your way down the curve of diminishing returns.

A minor change to check for the use statement having params, or the module being called having an @EXPORT (compulsory export) would largely resolve your issues.

The poster is not going to automagically modify the files, he's just looking for clues. If a report can identify the 25-75% of obvious cases, then it's a good high yield starting point.