The Epilogue section is apposite here; in summary, a large number of
passes is a redundant catch-all for different magnetic encoding
techniques. A sensible change to make to shred might be to use only
those passes relevant to current and near-current HDDs. The load spike
referred to won't go away with a reduced number of passes, it would just
be shorter-lived.
It's tricky to view security/performance tradeoffs to be anything but
ratchet-like, only ever towards security. Perhaps it's even preferable
to make --iterations be a mandatory argument, except for the breakage
that would cause to old scripts.
Why 5 passes, and not 3 or 7?
BTW, are you also working to add solutions for journaled filesystems,
such as the "s" (EXT2_SECRM_FL) attribute? (I have no knowledge that
this is effective, but the API certainly exists.)