If not "study," I'd strongly suggest doing regular "homework" for your work.
For instance, unlike in the early days and well into the 2010s, most mobile UI and UX are solved. You know how users use apps and how they want something to respond to. However, I still find many people in tech, even after "years of experience," always think about their company, their app, and how specific actions of the users impact them. I usually ask them, "What about the customers and the users?". Remember that for most users, your app/website is just one of the many they use.
This simple example is easily resolved by doing regular homework—studying how others do things and how users use their apps.
I think "looking things up all the time" (plus "figuring things out all the time") is the primary method of how I learn. This was the case back in college too - solving practical problems (homeworks, projects) was the best way to actually learn stuff, just reading the textbooks caused most info to disappear right after exams.
I study things that I'm interested in that would be useful for my job all the time.
I sometimes study things specifically for my job.
Yes. It has continually had an impact.
I read up on the latest in software engineering for my own benefit/interest. I don't do anything at all for my job outside of work. Whatever skills I gain I may use at my job later, or I may take them to a new company.
Yes. The curse of being an expert is having to maintain that expertise.
minimum 1hr of every day at work, since 1999. no need to deal with work/life balance, it is part of your work and to be done during work hours.
Continuing education is mandatory in many fields. In tech, no one forces you to do it, but if you want to keep your skills current, then you have to study—not only to keep up but to get better. If you don't, then you won't have much of a career. So, yes, many of us continue to study.