Though you yourself built a false dichotomy with a poorly-done "unskippable" tutorial. How about a well-done skippable one then?
Back when FLStudio was Fruity Loops, it had a cool modal-driven (skippable) tutorial for various features you could opt into in the respective component's "?" menu, like how to get started with the piano roll system or the fx system. And frankly the UI was already pretty intuitive, it's just not obvious where to start when you're a beginner.
Btw, unless it's a toy/trivial project or catastrophically dysfunctional, one does not merely redesign a UI. That's been the main driver of second-system effects I've seen in the wild.
1- Talk to your users. Watch them using your interface. Ask them what can be improved.
2- When direct access to users is impossible (one example can be: your work goes to another software company which in turn has access to those users) then you use it. Start making at least 100 entries using your interface, that should cure you really fast of your ivory tower. You might lose 2 or 3 hours but trust me, your interface design will improve ten-fold.
I acknowledge that some interfaces may be needfully complex, in which case this tool might be useful. However, I suspect more often than not, this tool will enable frustrating, disorienting, and confusing tutorials to a degree where they become even more pervasive.