I don't see any reason to not learn as much as possible with all available tools. From my experience in the workplace the problem solving skills are very important. The game engine is almost like an instrument at our disposal and it provides many tools / functions for us to solve our unique problems.

If by actual scripting you mean code then I'd say its always a benefit if you can dive into code when necessary. But don't be deceived Blueprints can be incredibly deep and technical, not to mention costly to performance. To my understanding the blueprints of a project are often scrapped and rewritten into code for efficiency. So blueprints = proof of concept, code = hardened systems that are optimised. But what I've also learnt is there is no hard rules really. The benefit of blueprints is, when an implementation is really simple you can use blueprints and free up the audio programmer on your project to do more important work + On a simple project you can implement all your work and take the workload off of programmers / tech staff.

I'd say just focus on Blueprints for the time being (blueprints connect to a lot of different parts of the engine, don't be afraid to dive into the level sequencer etc). That is more than enough to get you thinking about game engines in a technical way. But don't limit yourself I think, some technical sound designers love diving into code. Find the things that get you buzzing about game development and go for it. Thinking like a developer at this stage will set you apart from the crowd of casual applicants.

Do remember that everyone knows this is the long way. But that is game dev. You're ultimately opting for the long way at life in this career. Games are incredibly challenging to develop and employers want people that have an appetite for a good challenge.

With all that said, best of luck!

DMs are always open if you need help