Great list, but it's worth remembering that there are some organisations you might personally want to work at, whether that's for money, a great resume, experience, location or some other factor, where asking questions like this could get you marked as a troublemaker and result in you not receiving an offer.
That's not to say you can't work on the worst issues when you start, but sometimes you have to choose your words carefully.
Also related, this article.
That's a very good article, thank you!
It's your choice!
Personally, I wouldn't want to work in a company that labels me as a troublemaker for trying to understand if I like working with them - interviewing is a mutual process, it's not just them walking around the local market and picking the best pumpkin 🎃. And I probably wouldn't feel comfortable working there.
Then, many of these questions don't have the right or wrong answer - they will help you understand the company better and pick one being informed and prepared.
Maybe you'll have to make compromises, but at least you know what you are doing.
Finally, I think that it depends on the position you will work on. Maybe if they're hiring the first technical person ever for the CTO position, it's possible they don't have a plan for you - you'll have to do everything yourself :). (I've never done that, just guessing here.)
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.