Haven't tested that with iLO's yet, but I've had some similar issues with some Appliances, firewalled machines, KVM's, etc. I think Lansweeper "classifies" machines depending on which services answer first, so we get those issues.
What I've done is just edit the Asset, and fix the "Asset Type" to whatever best fits the machine, just check the padlock checkbox next to Asset Type.
If your iLO devices use fixed IP Addressing, you can also do a IP Range entry just for them, and them disable SSH and Windows detection (those are the only ones that can disabled, AFAIK). Of course, if they are on DHCP or are transient in nature, that won't work very well...
I'm a bit surprised SSH works (never tried on ours), since it requires dmidecode, sudo, etc, but iLO's also support SNMP, so maybe you can set an SNMP credentials on that range, our multi-protocol devices (printers, etc) seem to respond better to SNMP than HTTP/HTTPS...