Hello Artbyrobot
I've just found your thread. I'm working on a "similar" project - but with a completely different outcome in mind
That said, I see some interesting cross overs - and I'm not going to lie - some of your points have inspired some considerations for my own project.
That said, and focusing on your specific desired results - I think there are some fundamental aspects of the orginal concept that you might want to consider.
1.
What is the specific driver for the "robot" to look / pass for a human? On a purely physical level - a human is a human based on evolutionary needs - every aspect of human physiology has evolved to help the organism thrive in it's natural habitat - however, it would be stretch to say that human physiology is "perfect" - so the question is, why constrain your design to mimikry of a "flawed" design - when you would have the ability to tailor your physical result to your specific use case.
2. While you seem to be putting a lot of effort into the mechanics of movement and physical replication - ultimately, the biggest (understatement) hurdle you will have is the "Brain" - you use the term "Robot" - and this has a specific definition in engineering terms - but to be specific - are you looking to create an Android or an Automaton? There is light years of difference between the two products. Assuming you are looking to create an animatronic "human" - then, I'm sorry to say, there are lots of resources that you could follow to get the job done without - well - "reinventing the wheel" - a lot of the challenges you are or will face - have already been solved for animatronics and there are even D.I.Y projects that you could follow (and improve upon) to get to your goal quicker and without the waste of resources and time that is native to this type of project.