@Temoran Hey Alex, sorry for the late reply here. My advice is likely similar to what you've heard before, but it's still pretty far from your "plan", so it may be worth hearing/reading again :)
My advice -Don't spend a year learning Vue + API, then learn python & flask... Instead, pick a SMALL problem that you can work on over the next week, and learn just enough to solve that problem with a single toolset (preferably Laravel since you're here).
Once you've solved that, you'll likely think of other things that you can add on. EG: You created a "chatbot" that takes in user input & hits the OpenAI API, then spits back the results. Awesome! But now, make it look better (learn enough Tailwind to do what you want).
Then, you realize that you want to have the cool "typing in real-time" effect from the AI response - so learn a bit about the Laravel HTTP streaming stuff (honestly I don't know much about that yet, but for the purposes of this example let's assume I do, haha), and how to use Laravel / Livewire / Alpine to display the cool streaming message in "real" time.
Long & short, my advice is don't try to learn technologies / languages / frameworks. Instead, learn how to solve specific problems, and then increase the scope of problems you can solve. My preference is to learn to solve problems with as few tools as possible (I haven't wanted to learn Flask/Rails because Laravel solves the same sorts of problems, for example... But Laravel isn't the right choice for things like Machine Learning, or interfacing with certain services that require python SDKs, etc..).
My advice is super old fashioned, but it's essentially this - Learn to solve problems with the tools you're comfortable with, and learn what problems those tools can't solve...
That's not to say that you shouldn't learn about other things (Vue, React, Flask, React, Flutter/Dart, Whatever) - but as you're looking at them, consider them through the lens of "How would this tool make it easier to solve [problem] than anything else?" OR "What kinds of problems are better solved with this, and is it worth using it in my workflow just to solve that specific problem?"