Here's an edited to customize for you version of something I posted to another potential career changer considering using a bootcamp to get there.
My college degree is in mechanical engineering, but I've only ever worked in computers as a developer and later a pointy-haired leader of same. If you have a passion for it, I think it's one of the best careers around. If you get into it because it's "good money", it can be just as soul-sucking and unfulfilling as anything else that you're just doing for the money.
20 years in, I'm comfortably FI if I wanted to downshift lifestyle at all, but because I still enjoy the work, still have kids in elementary school (so tied down from carefree travel), and can still find use for the salary to pad the stache, I keep doing it. My plan is to leave when the youngest is off to college.
For your specific question, if you have/had a passion for it, wouldn't you already be doing it? Mid-30s is a tiny bit late to be jumping in from scratch; it's by no means impossible, but there is some age discrimination across the industry (more smoke and complaints than fire from what I've seen and personally experienced, but beware it's a possibility). Realize that this industry is much more about what you can do than who you are, meaning if you're a fresh bootcamp grad in your mid-30s, you are directly competing against that 21 year old college grad and if they came from a compsci background, they are probably better than you. You will have to prove yourself as capable and you'll make the same wage as the new grad. (Wages in the field are crazy high, so that's probably an upgrade from most of the non-profit sector.)
I am not at all a fan of the bootcamps. Too many bootcamps are in business to extract money from students than to educate them with a solid foundation of computer science principles (which, to be fair to the bootcamps, cannot possibly be learned in 10-12 weeks anyway). Would you be able to find a way to cram an MBA into a season? Presumably not, which is why bootcamp grads aren't looked at anywhere near as in-demand as comp sci graduates. That will eventually go away, provided you continue to supplement your knowledge continuously as the industry evolves.
There is a lot of pure-remote or location-independent work available in the field technically, but just like any other teamwork job, it's easier to work with other humans when you're in the same location, can eat/drink together, etc. For your initial 4 years, I wouldn't even consider remote work if it was offered to you. You need to be on teams, working everyday with developers who are better than you. Initially, that will be "almost all of them", but even after 2 years when you think you know most everything, there's 50x more that you don't know than do and it helps immensely to not be the smartest person in the room / team. (If you think you are, change rooms.) Once you have a handful of years of experience, then you can reach for the brass ring of all-remote work if you decide to go that route. Because you mention the social aspects as appealing, this advice is perhaps even more relevant to your situation. Working as a contributing member on a strong development team is super-fun, IMO. People in the field I find as generally supportive and interesting to work with, provided you put in the effort technically and socially.
I love the field. I'd honestly do it for half of what they pay me, maybe even for a third. For me, it's like getting paid to play an open-ended intellectual puzzle game constantly. If you don't have that same passion, I'm not at all saying that you can't become good at it or that you can't build a good career in it, but just that you have to discount my inherent love for it when considering the burnout and fulfillment question.
In terms of being a female in the field, you will be an extremely welcome mathematical minority. There are a few toxic workplaces, but I think for the most part the computer programming field is a meritocracy and most of it is extremely intolerant of intolerance. You may need to speak up a bit more to be heard initially.
