I'm really against removing the defaults column, if there are issues with a setting it provides more info to your host (who users will generally be reporting to) about the very small default values; these checks are generally for servers who just installed the module for security and didn't really configure it.
I pretty much designed this system for the admin to screen shot it and provide it to the host, as your host generally wouldn't have admin access to the UBB control panel. Thus, the links to the descriptions of everything wouldn't be passed along with a screenshot. The links are there so the admin can go and see what each variable is for, basically to enhance your argument that the setting should be increased.
The "unset"/blue wording will be very rare to see, outside of test code as when the module is installed via apt/yum or even compiling it manually, it should insert default values for these items.
And no need to "chill out", I'm perfectly fine; I'm just trying to provide details as a knowledgeable person who worked helpdesk and server administration for a webhost for 9 years; what is displayed there is the data I'd want to see vs being bombarded with links to various config options on a site vs just having the data displayed for me would make me want to go and look into the issue...
