I can provide my anecdotal current experience. I just started a new role in a remote position with less "work experience" (vs. personal projects) than you and I

I can provide my anecdotal current experience. I just started a new role in a remote position with less "work experience" (vs. personal projects) than you and I can say that the autonomy is not an issue. I'm working on a complex, undocumented, "created-here" and over-engineered C++ code base left behind by a senior programmer and have found there to not be an issue. Granted there is a bit of a ramp-up time as I'm learning the code base but I ask questions in our chat application whenever I get stuck and my teammates are pretty responsive. I've actually found that I'm more productive/learn the code base more when I'm remote than when I visit and work in the office. In the office I use the other programmers as a crutch and they end up spoon-feeding me the solutions because it's easier for them. Remote, I make more of an effort to understand the components independently. I wouldn't be too worried about "getting stuck" in the code. The larger and uglier the project, the slower it is to learn the components but I've learned to embrace getting stuck. It's part of the process and once you've figured it out you know that small part of the code base a little better.