The primary reason that the JS API methods and input value updates don't trigger event handlers today is that it preserved the previous behavior before the launch of event handlers and facilitated a safer migration to the new feature set.
I agree it is better for dry code and is easier to understand, and expect there to be a point in the future where components all have separate 'User input" and "Value change" events that can be fired. For the option of adding a flag on JS API methods, it would likely need to be implemented as a default of not triggering otherwise. I've talked with a few users about this behavior and will resurface it internally when we are next able to do a pass over the general event handler system.
I'll move this thread over to a feature request to help track the general discussion on the topic 