Enterprise/corporate issues are often WAN facing servers, port forwards and BYOD but some of those vectors are open with home users, SSH on routers/ap's, telnet on printers, 80/443 gui's on IoT, etc.. However other attack vectors still impact home users such as malicious URL's, scripts, exploits, rats, and other things. Cylance addresses many areas of attack, but doesn't address all of them. That was my point - you may want to pair it with something else, whatever that something else is - up to the individual.
I suppose testing is in order, but the average joe might be sufficiently protected by Cylance if they simply added a nice browser filtration extension like WD for Chrome or whatever. However I still would feel naked without something watching the traffic and I wouldn't be 100% confident with only-Cylance. (me personally) Heimdal makes a wonderful companion to Cylance on endpoints IMO.