All of it is by choice only. You don't need to use ORM or any inheritance in your code. Whether IoC happens depends completely on how you write code, but the service model in .net is there if you want it. (And you should try if you haven't - it's really good) You can go as basic as you want and rawdog everything without frameworks/libraries.
These arguments (for any language) are pretty lacking. That you can do it isn't important - the majority culture is the deciding factor - since every internet resource, every package, every support forum is going to follow the majority culture. So not following it simply adds friction. It makes way more sense to choose something where the majority culture makes sense for you, assuming it exists.
That's very far from what I see in practice. Apart from EF, I haven't really experienced any library which forces any of the listed things on you. You can choose some framework if you want of course. But it's trivial to stay away from those.
All of it is by choice only. You don't need to use ORM or any inheritance in your code. Whether IoC happens depends completely on how you write code, but the service model in .net is there if you want it. (And you should try if you haven't - it's really good) You can go as basic as you want and rawdog everything without frameworks/libraries.