Smarty templating is optional but easy to set up. Smarty seems to be a religious topic for PHP developers. Switching between Native views and Smarty views for a controller is done in a single annotation on a per controller basis.
The trade off between wasted processing and elegance is not high enough for most people. I could see it being nice if you are giving access to "non-developers" to modify the views/templates of your system and want to make sure they only have access to a given subset of functionality.
You're ignoring quite a few features of Smarty, and I disagree with you on human readability.
The other reply also wasn't saying anything about ease. It was about control, which is also important once your team reaches a certain size/level of skill diversity.