You don't need to sign up for bitcard etc. You just need to run the perlbug command-line client.
As for it's 'just one line'. What actually has to happen is that *someone* has to read the links you've provided, understand the issue, decide whether your patch is the best way to fix the issue (perhaps there are other considerations?),
write an informative commit message, run the test suite, push the commit,
and deal with any fallout if the smokes start failing. And field any queries from other p5pers, even though they aren't necessarily the one who understands the issue.
Whereas a bug report / RT ticket gets emailed to every one on the p5p mailing list, and the person who most understands the issue and/or the one with the spare time to apply the patch gets to deal with it. And all correspondence is logged against the ticket for future reference.
... and deal with any fallout if the smokes start failing.
Do the smokes even deal with performance, or relative changes in performance? I'd be concerned that a "fix" might solve one performance problem in one corner of the space, and introduce others in other places.