I'm not sure I understand your question. Are you asking for a list of the hundreds of commands which did nothing useful when run as cmd -h or cmd --help? I didn't save that, and as mentioned, it'd probably be different on your own systems/with your own packages.

If you want to try this at home, you should maybe either have GOOD BACKUPS HANDY OR DO IT WITHIN A VIRTUAL MACHINE/CONTAINER (EDIT: and almost certainly NOT AS SUPERUSER) also be ready to kill processes that are hanging waiting on stdin or somesuch. You're likely to have a least a few.

WITH THIS WARNING BEING GIVEN, you could just:

    (for cmd in /usr/bin/*; do echo "CMD: $cmd"; "$cmd" -h; done) >/tmp/dash-h 2>&1
    (for cmd in /usr/bin/*; do echo "CMD: $cmd"; "$cmd" --help; done) >/tmp/dashdash-help 2>&1

Of course, you could try /bin if that's any different (for me it's a symlink to the same dir as /usr/bin these days). You could also do single dash help.

If you want to accumulate some stats yourself, then you'll probably want to postprocess those output files.. So, you might also adapt the embedded echos to make it easy for whatever you like to do for that. Or, alternatively, you could re-direct each output to a per-command file with a little ${cmd##} massaging.

EDIT: and if you're asking what the CL syntax conflict was, well, I only meant to refer to "How to get any help at all - command with no args, with -h, -help, --help, -?, etc." as that is kind of the "very first question" on a user's mind. There are other syntactic conflicts (combining bool flags, option-value separation, unique prefix matching, etc., etc.).