While I'm also not nearly as educated as I'd like, I can say that the perk (for me anyway) to starting with DBP is the fact that you can type away, mash that shiny F5 button, see it either run or fail, fix/improve, repeat. Later on I dabbled SLIGHTLY in C# and HTML (and a microscopic amount of LUA). Thing is; a programming language is a programming language. ALL of them have core values. Pay attention to the stack and heap. Keep in mind a general idea what's loaded in RAM and when. Each line is executed sequentially. Everything has a more or less standardized syntax.
Therefore; going deep into DBP will actually AID you when you hit other languages as well. You'll find similarities and obvious differences. You'll develop that eye for how to follow what's going on even if you don't understand every command, and develop context clues. So, yes. Go for DBP. If for no other reason than it is a HIGHLY educational journey and can produce actually good results if done right. I've seen enough bits and pieces to feel confident that a game made in DBP could be confused for a game made in Unreal and vice versa.
TL;DR stick with whatever feels solid to you. I just recommend DBP because while it IS friendly to work with, that doesn't mean it can't do big boy things too
EDIT: the "spoiling" aspect might be present to A DEGREE. But I'm given to understand numerous other languages spoil the programmer in other ways. Lots of people have programmed in more recognized languages who never put a second thought into optimization, only to (if they care) double back and research how to code closer to the hardware than they ever intended to. This language too also has those teirs. So whichever you go with, don't let FOMO get to you.
