Publish Service Fabric Application - How to leave Local Cluster as Default in connection endpoint

Question

In some recent releases of Visual Studio and Service Fabric Tools, I noticed that the option Publish Service Fabric Application takes a long time to load the clusters I have access and after one minute it throws an error saying:

That didn't use to happen before. Also, when the failure happens, the Service Fabric Tools pane shows a lot of "A Task was cancelled exception" and "Could not get access to the shared lock file". Also, it freezes my Visual Studio for quite sometime.

That said, I would like ask if there is a possibility to never load the clusters you have access and always leave as Local Cluster as default in the Publish Service Fabric App > Connection Endpoint, since it takes ages to load the available endpoints that I'm not even using.