The same location needs to be shown differently to different audiences.
A client would want to see a rendering with finishes and realistic views. A contractor would want to see their specific trade like MEP, drywall, flooring, etc. A code official would want to see the building systems like structural, lighting, HVAC, fire protection, and other systems the codes specifically call out. A fabricator needs very specific shop drawings for the parts they are going to make. It is often not beneficial to show everyone the same view, because that would be too much information and the confusion can hinder you from getting the important information across.
View templates enforce consistency across a set.
View templates help keep a project consistent, and without them things can get messy quickly. When views are configured individually, line weights, visibility settings, and annotations can vary from drawing to drawing, making the project harder to read and coordinate. To avoid that, templates and standards should be managed by the BIM manager or project lead so everyone is working from the same setup and the project stays organized.
You published two versions and compared them.
Version history becomes especially important on a shared model because multiple people are making changes and everyone needs to know what was modified and when. If a consultant says they're working from last week's version, you need to be able to tell them exactly which version they have and what has changed since then. A model should be formally issued whenever it's being shared with consultants, clients, or contractors, since an issued model creates an official record of what information was released and when, while a simple save only updates your working file.