Yeap, I’ve often ran into the need for this too, and arrived at the same solution. The downsides to this are:
When run, this shows up as a different workflow executions. This may make it harder to troubleshoot.
If you have two different instances of N8N (like separate environments) and export from one and import into the other, then the workflow ID’s will be different and this will break. I had to come up with an export/import script that patches workflow ID’s.
It would be great if N8N implemented a native feature by which you could reuse parts of your workflow, like with BPMN Call Activities.