Hi,
Well, yes and no. If you use the "blocked zones" or "authorized zones" setting of the geolocation plugin, the plugin will load HikaShop to be able to check if the user should have access to the page as long as the current component displaying the page is listed in the "components" setting or if you left "all" in that setting. So it will have to load HikaShop even on pages where you don't have HikaShop displaying stuff. And if HikaShop is loaded, it will add these CSS / JS files in the headers of the page as it doesn't know if a module will need them or not down the road.
Also, regardless of how you configure the plugin, as long as it is activated, it will have to load HikaShop on the first page the user arrives on your website to calculate the zone of the user from his IP address (that's the goal of the plugin), even if the page doesn't need HikaShop. That's because the plugin doesn't know in advance if that first page will need the zone of the user or not later down the processing of the page (in a module for example).
So first, I would recommend checking the settings of the geolocation plugin. For example, if you're using the blocked/autorized zones settings of the plugin and you only want to block HikaShop pages in some areas, then you should enter com_hikashop in the component setting so that it doesn't need to load HikaShop on other pages than HikaShop pages.