I think that changing which states would affect global state of host by user would cause a lot of confuse. States already define "relevant?" method, so when e.g. puppet is not used, configuration status is not relevant and not being saved hence not even displayed in host detail. I think what we need is customizable host table column list (per user) so people interested in specific state can see only that one. I'd say that global status should remain untouched at least to keep searching and API consistent.

I agree with Marek. Either a customisable table, or somehow showing all detailed statuses in a minimal way (like miniature squares next to the status icon), may help.

Either of those sounds fine - my concern is that, as a user, I've potentially lost an overview. Sure, I can mouse-over or drill down into a host page for all statuses, but the at-a-glance health check is gone.