But in practice I see a lot of 'OOP' code that is just procedural code that is split up in 'sub-procedures' that are classes. And then there is a Program or MVC-action that just runs one after the other call to those services and passes intermediate results between them.

This also what you see in the super-modern CQRS architecture: a dispatcher calls a handler that does some stuff in a certain order to make a result. That is in essence procedural programming with some stuff around it to organise it.