Have Trouble LSP window ALSO list diagnostics??

[unphased]

I think it's interesting with trouble v3 to use the single Trouble lsp window to be able to preview and hop to definitions and references etc. Even though I got used to having separate binds for show/go to definition and show references from trouble v2, I have no problem adjusting to using a single pane to access both defs and refs.

I also occasionally like to use trouble to get a navigable/previewable list of all buffer diagnostics (or project diagnostics). But I don't usually think to open it. I'd like to opportunistically make the list of diagnostics visible...

I was wondering if it's possible since standard Trouble lsp usage already puts multiple categories together, to have diagnostics added as another category in it, and this would give me an excuse to keep Trouble open more often to keep tabs on diagnostics and remind me to whittle them down. I hope if I can get used to this I might disable diagnostic extmarks which will make the buffer less cluttered. I think that will make the experience of editing a buffer filled with diagnostics less overwhelming.

I also had another question that relates to this. I'm currently using a bind

      {
        "<C-t>",
        "<cmd>Trouble lsp toggle focus=true<cr>",
        desc = "LSP Definitions / references / ... (Trouble)",
      },

This command fails if i trigger it while my cursor is not on a valid lsp token.

How can I adjust so ctrl+t will always toggle open Trouble lsp? In particular i'd like it to focus into the trouble window if my cursor is on a valid item, and if my cursor is not on something useful, instead of giving a No results for **lsp** yellow error, to open the trouble window without focusing it (though it's fine for me if it always focuses it...). Per the above concept, by cursor being on nothing valid, I want it to just list buffer diagnostics!

I hope this can be done.

[unphased]

If this is not possible and a trouble window must only be in one mode the workaround is i'd have to keep and manage a separate trouble diagnostics window around to use this for, which would be too much manipulation overhead and i would not use it regularly.