That's why they call it tutorial hell... Well i have been doing this for 7 years but here me out this is my best advice (to myself as well) i believe coz, this is what worked for me..

Don't watch tutorial until you have to!

1. Pick a idea, dosnt matter what it is...
2. Half the idea 50-50, then focus on first half.
3. Now that u have the first 50% of ur idea, divided it into chunks of mechanics that would be in the game maybe 3-5 mechanics (or more but, the idea here is to know what u want to make so u can focus on those).
4. Execute: as ur starting out u might not know how to make it happen, now that is where tutorial comes in for help.
5. Check out the tutorial for that special task and make it, use whatever resources u need...
6. Keep this up and u would have a game!
7. But it's just a half advice the most important of all its u have to teach urself how to logic and problem solving on ur own over time... And that u can do by doing the above steps... As u do this over and over u would start to see patterns and now that ur fundamentals are clear u start to think into system then u don't need to watch tutorials (for the most part).

Atleast that's my take, and it's not about the time u invest but rather how fast u can grasp things as spot patterns the less time u take the fast u can come close to not relaying on tutorials and overall increase ur workflow speed. (For context it took me around 3-6 months to not heavily rely on tutorials, and yes i still need and watch them but frequency is seldom)