One thing you can do is let people flounder and fail on irrelevant small tasks for a week or two early, to help them learn the lesson that they don't know what they're doing.
The best way to make someone appreciate guidance, is to have them fall on their face, receive guidance and notice the difference.
One suggestion I had was, if you're stuck for more than 30 minutes, ping me. Juniors will almost always be stuck with something trivial you can answer within a few minutes. It gives you a break and it is something they really appreciate. If you communicate to them that they're not expected to know anything and that the first few years on the job is their real world education and a chance to ask questions without raising eyebrows, they'll be far more likely to do it.
Juniors are nice in my experience, you can mold them into something half-decent if they've got a bit of a brain and their mistakes are ones of innocence, not cunning or apathy. It's the 'senior' devs who don't know shit that you have to put up with that's almost always a disaster. They'll be well versed in lying and politics, wasting everybody's time.
I find that a balance can be managed if people are nudged to at the owner of the specific component they need help with, i.e. @guild-frontend or @owner-fooservice
Exactly the same here for exactly 20 years. I make my own products and make products for other companies as consultant.
No real problems when I need to hire subcontractor though. Being an old fart I know many very experienced people who would never pass an opportunity to make some dosh.
I like remote working, and I've done it on and off for more than 2 decades. It suits me.
In my experience, mentoring junior devs and new hires on my projects is much harder for everyone involved when you're not in the same office. Sometimes you're lucky and get someone who'll speak up and ask questions when they get stuck, but often (especially with juniors) people will just try to figure things out on their own in order to not look bad at their job or incompetent or something. Some devs would rather spend a whole day on a problem and only bring it up in the following day's stand up than show they can't solve it alone. That is really bad for a project. I find I have to poke the quieter juniors regularly on Slack just to make sure they're OK, but then people get annoyed about being micromanaged. This is something I really want to solve...