First, asking questions is not what I consider dumb
The VSS framework is a solution from Microsoft that allows to take backups from files or applications (for example, Exchange and SharePoint also have a specific VSS writer) even if those applications are running. (Remember the good old days when you had to create scripts to stop a certain application before backup and start it again after backup...). Through this VSS framework this is not necessary anymore. You create a snapshot, you can take the backup, and release the snapshot and all applications were continuously running. PS: That service comes with SQL DB and not with Endpoint
I am not going into much detail about VSS but in essence you have a requestor (in this case, a backup application), a writer (specifically for the app, so SQL, Exchange but also for the file system, WMI and so on and so forth. Run vssadmin list writers in an elevated command prompt to see the ones that are in use) and finally a provider (kind of the service that is the "organizer" of this and arranges everything between the components).
Even if that service is running, it won't take resources. It will stay idle until it is being "called" or "requested" (so only during backup)
If you let it run, basically your databases (although it is probably only the one from Endpoint) will be requested to get into a consistent state and you will not end up with a potential data issue for that database
If additional questions or still not clear, let me know