Commerce Kickstart Taxonomy: Understanding its purposes, functionality, and logic?

I believe I originally posted this in the wrong place, as I didn't know I could make such a post as an issue. Most of this post is somewhat of a recap and a guide for other new users with similar issues. My main questions are in bold at the bottom.

Newish user to Drupal about 3+ months in the process of learning the functionality of the relationship and set up between Menu links, Commerce Kickstart's "Collections" view and Categories set up, via Taxanomy vocabularies using the Commerce Kickstart Taxonomy menu path and module. As a newbie to Drupal Commerce and Kickstart I must say you truly get hit in the head with a hammer of confusion the moment you try to do something as simple as setting up or editing a Product Category vocabulary the same way Kickstart is set up. Something I would assume a lot of users want to change, and even if they don't, they would at least want to understand how it works.

The issue or confusion immediately sets in when a new user wants to change or alter the Product Category vocabulary(in a non demo store) or Collections(in a demo store) name or path or in my case, add an additional custom vocabulary and try to set it up with a similar view to Kickstar's "Collections" view.

Issues from the point of view of a new user:
-If you disable the "Collections" view, then any menu tab created by the Product Category or Collections vocabularies disappears. This is despite the fact that the vocabulary still exits in Taxanomy(Categories), and the option to synchronize changes to the vocabulary with menu links is still checked for that vocabulary.
-If you select the Commerce Kickstart Taxonomy for your menu path for your new or custom named vocabulary, nothing happens.

So after digging around for a few days and messing with it extensively I was basically able to come to the following conclusions which I hope will save some time and clear some confusion for others and I hope more advanced users can chime in and clarify.

-If Commerce Kickstart Taxonomy is selected on the Taxanomy vocabulary page, under Menu Path, it will automatically intercept Drupal 7's creation of its default pages for taxonomy vocabulary terms and taxonomy path creation but ONLY for the vocabulary named "Product Category" in a non demo store, or "Collections" in the demo store. A reasonable assumption being that you would want the Kickstart custom "Collections" view to show up at that term address as opposed to Drupal 7's default view of teasers which it creates for any taxonomy vocabulary term.

-More specifically, it alters the machine name and system path, so instead of the path "taxonomy/term/term ID" it will rename it to "product_category/term ID." You won't see this if you are looking at the aliased URL's, so check the actual system path to notice the difference.

Edit: It appears as if whether or not you select Commerce Kickstart Taxonomy or Default under the Menu Path Type when editing a "Product Category" or "Collections" vocabulary makes no difference, as long as the module is enabled. Even if you change the menu path type back to default, delete your vocabulary, and rebuild it, it will still create all system paths as product_category/term ID as opposed to taxonomy/term/termID. The only way to truly revert back to default appears to be by way of disabling the module, and recreating the vocabulary. It also means that even if you alter the module to include your custom vocabularies, if you already have created the vocabularies using the default menu path, it will not automatically rename your system paths to your_vocabulary/term ID, even if you select Commerce Kickstart Taxonomy menu path unless you delete all terms and recreate it from scratch after enabling your custom module.

-The menus created by the vocabulary disappear when disabling the "Collections" view. A reasonable assumption for this is due to the fact that Drupal 7 doesn't let you create a menu link to a path that is nonexistent or has no existing content. When you disable the "Collection" view, you are removing any content from the corresponding Menu link page. Since CK Taxonomy intercepted and prevented Drupal 7 from creating a default view at that same path, there is no default view to show in its place. Drupal 7 removes the menu links. They come back when you re-enable the Collections view. Sometimes. If not, simply go to your Product Category vocabulary, edit, and at the bottom check the option to rebuild the menu on submit.

-Since the module only specifically targets vocabularies Product Category or Collections, if you want it to set up a custom vocabulary with the same system paths and a similar view, you will be required to actually alter the Commerce Kickstart Taxonomy module and add your vocabularies name there, in code. There is a great post by Sj1 posted under a similar issue, which is very helpful that details what is going on and offers help on how to do this.

-I ran into a comment where one of the Kickstart devs stated part of the need for this module was to handle the choice by users on a fresh installation of demo store or no demo store, which picks the appropriate menu vocabulary and corresponding system paths.

As a newcomer to Kickstart because of hearing about its ease of use, to offer a bit of criticism, I must say that this issues is nearly system shocking to have to run into as soon as you basically start learning how to set up a new store, and all you want to do is to change the Product Category vocabulary name or create an additional similar set up and view. To run into issues such as having to figure this logic out with so little and hard to find documentation, and then end up with the solution being altering a module using PHP, which then requires you learn a thing or two about module creation....suffice to say...it doesn't quite fit the idea that Kickstart is easy to get up and get going. I personally had to backtrack all the way to Drupal Commerce and then Drupal 7 Core to install some of the modules and play with them extensively before finally figuring out what was going on, and that still required the help of the posts scattered throughout Drupal 7 forums. All that for changing the name of your main product category?

Which leads to my remaining questions. Are those the only major purposes of the Commerce Kicktart Taxonomy module? If so, why was this route chosen as opposed to another simpler method of overriding Drupal 7's view? What is the advantage or reasoning behind doing this way using a custom module as opposed to something such as using Views to override it? Views comes built in with a Taxonomy Term view that allows you to Drupal's taxonomy term pages by simply enabling it, and has the ability to even target a specific Vocabulary name for overriding it with a custom view so I have to assume there are other reasons for going this route which adds such a crazy level of confusion and complexity. What are those reasons? In order to move forward I need to know which route to take and in order to do that, I need to know the differences between going the route Kickstart is doing it, using a custom module similar to Commerce Kickstart Taxonomy to change system paths, or using another method to override Drupal 7's taxanomy term pages.