No, that would be total overkill. K free will prevent the vast majority of malware that one may come across. To discuss what will happen with a true zero day sample (taking my ransomware as an example), let's consider that the user first installs K free, then CF at my settings:
1). Installation- First off, CF will block the Kaspersky Secure Connection module (ksde.exe). This is probably due to KF19 not being generally available from the Kaspersky main site (a download from there still will result in KF19. But whatever, just change it to Trusted and you are Golden. One may also see that avpulmain.exe is sandboxed on KF update
2). On boot note that KF will both evaluate what is running in RAM as well as looking for malware sitting innocuously on the system. For example, I plopped a Locky C in my downloads folder (had to do this with KF disabled) and rebooted the system. On boot KF saw and deleted that file. This is very good, but be prepared for a bit of initial sluggishness on System Start.
3). Zero-day stuff- Taking the ransomware I mentioned previously (that Ophelia coded), running this will not result in a peep from KF (nor any other product) but will yield a CF popup that the file was Contained, and a Windows popup that the file cannot be run- as well as the file being deleted. This would be due solely to Comodo.
So quite frankly I do not see a reason for complicating things with any further security addons- KF has excellent protection against known malware, and CF will catch KF when it Falls (by killing true zero-day stuff).
ps- One really doesn't need the HIPS with this setup unless One likes to be annoyed by popups.