Looks like it’s just HTTP Requests for secure connections. You can always create a TCP Out to HTTP Portsets rule to get rid of the log spam but it may be triggering because of Global Rules or Network zones. What are your Global Rules?
Global Rules:
Creating restrictive rules for svchost isn’t needed really and can cause some problems. Any malware or unknown file that is a parent process of svchost, those svchost connections will be blocked, particularly if you are using the CruelSister setup.