What exactly is missing for you with your current solution? Is triggering Drafts in a particular way just faster for you? Triggering Drafts to do more than just the built in functionality is likely to require Shortcuts, so if it does happen to purely be a speed thing, you may be constrained. Drafts can obviously do things itself without Shortcuts, but automating that triggering is what I am referring to here.
Drafts is great for capturing content to process later and content you know you want to keep in Drafts. It sounds like you are coming at knowing what you want to do - in Obsidian, but then wanting to take advantage of something about Drafts in the experience, and automatically push the content to Obsidian.
I’ve covered the speed aspect above, so if you are looking for speed, going via Drafts if the destination is known each time may not be the fastest option. Writing directly to a file in your vault is the most direct and maybe just switching to dictation and triggering via Siri might give you the speed if that’s the aspect you seek.
I often capture content into Drafts and sometimes I will push it on into one of my Obsidian vaults. I have created actions that help me do this. I use Drafts for capture to Obsidian on the go because I find the Drafts capture experience familiar and if I want to decide as I write where and what to do with the content, then this is perfect. The Obsidian experience is also quite slow on mobile, especially if I am switching between vaults.
It takes me one tap to finalise content in Drafts and send it to an Obsidian vault. That isn’t a big slow down for me. Is it this step you are trying to remove? If so, how would Drafts know when you have finished your content and it is time to send? That’s what the action does for me, so I can’t see a way around having something at the end to say I’m done, go ahead and do stuff.
The approach Rosemary discusses in the episode is that she tags her draft. Then, a separate device using the Pushcut Automation Server will periodically check for unprocessed drafts in Drafts for the Obsidian-related tag and process the draft. It will take the content and export it to the appropriate part of the file system as a Markdown file to include in the Obsidian vault, or send into Obsidian via a URL scheme (that detail was not covered in the episode).
While this means you have to have a second device dedicated to this, it would speed up the capture process because you would not have to wait for any export to finish. It means that if you have spotty connectivity too that this will just be automatically picked up once Drafts’ background sync next completes and the next automation server run occurs. The other downside is that you could be waiting a while for the content to make its way into your vault. even if you have good connectivity, if you just missed an automation server run, you’ll be waiting until the next run for that note to appear in Obsidian. You also always want to make sure you add your tag after you finish. If you miss the tag, nothing will happen processing-wise. If you add the tag before you finish, you could find the automation server job runs and only puts part of your note in place.
You could utilise other solutions to regularly check and process your drafts. Shortcuts is capable of querying and processing Drafts, so you could run this on a periodic basis through a scheduler if say you had an always on Mac, or maybe as a Shortcuts automation trigger on your iPhone/iPad - might need a test to see what it can run in the background, and remember it might take over what you are doing one your device when it runs.
My advice would be to identify what the ideal scenario looks like, then look at what you have as your resources and options. Once you have a clear view of what you want and have, then try to figure out how to address any pain points that those options incur.
Hope that helps.