NODES_INCLUDE - means only these nodes will be possible to use in any workflows (whitelist for loading nodes).
NODES_EXCLUDE - acts vice versa; these nodes won’t be possible to use in any workflows (blacklist for loading nodes).
I’m not aware of any options to customize the canvas, though
According to the official documentation, there isn’t an “easier” way to do this through the UI or via automatic configuration. The supported approach is using NODES_INCLUDE or NODES_EXCLUDE.
For your specific case (where you only want a small subset of nodes) NODES_INCLUDE is honestly your best bet. You explicitly list the node types you want to load, and everything else gets implicitly excluded. Here’s how it works in practice:
With NODES_EXCLUDE, the specified nodes aren’t loaded at all and won’t appear in the editor.
With NODES_INCLUDE, only the listed nodes are loaded, and everything else is completely omitted from the UI.
So yes, this actually has a real effect: nodes that aren’t included (or are explicitly excluded) simply aren’t loaded or shown in the canvas. There’s no UI-based shortcut right now — environment variables are the official way to handle this.
Unfortunately, to my knowledge, there isn’t a workaround beyond what’s currently documented.