This is correct. It was done by design to reduce the churn on sites. Flushing the cache for a large number of pages every time a post is updated via comments is not beneficial to caching in general. At this time, there is no separate flush for a post update vs a comment update. If/when that changes, then the new posts would flush more than the post update.
Also the for-loop for people with large numbers of taxonomies proved to be detrimental to load time :/
Right now, it doesn’t do it by design. In the future, I want to change it to be smarter and more exact.
