No worries.
None of the development on the apps based on my original understanding of your suggestion was wasted. Everything you asked for before clarification and after is built into the apps; not all of it is in the output of the apps, but even though "Usual causes" is omitted from the output, finding each of those lines was helpful in making sure all BugCheck strings were found on your page. All the work done was relevant and necessary, so the miscommunication ended up being a good thing in the long run.
FYI: Some of the links only work with the latest versions of WinDbg. I use 6.11 a lot, as many know, and newer BugCheck codes show up as unknown in 6.11, such as 0x133. For full link functionality, it is best to run 6.2.9200.16384 or a newer version.
If any links do not work, let me know, and I will try to determine why. Broken links should be replaced by a link to the long table of contents, so if the link does take you there, we may need to look into whether it is a bug in the program or a problem with the formatting of that particular BugCheck on the html page.