You can configure the node as you want it to be, and then wrap it as a component, and share that component in to your own local workspace, then in future you can simply drag that component in to any flow that you are building.
If you want to be extra fancy, you could recreate all the configuration options of the node that you’ve wrapped in this way, using configuration nodes with their default values set to whatever you prefer the defaults to be, that way if you find you need to change the values after all for a given instance, you can do so without having to replace the component with the native version.