"Dell Command | Update" shows incorrect CPU in System Information?

Cross-post from the "SupportAssist Enterprise" section (sorry!), because in retrospect, that appears to be the wrong place for this - please feel free to delete the original. Also, apologies if this is still in the wrong section, but it was the closest match I could find for the "Dell Command" set of applications.  Some searching indicates that these set of applications are intended for enterprise-level management of company PCs, but I have somehow ended up with it on my personal notebook (Latitude E6540).

In trying to decide whether I need both "Dell Command | Update v 4.1.0" and SupportAssist (and I seem to also have both "Dell SupportAssist" and plain "SupportAssist" installed), I noticed that Command | Update lists "Intel Xeon" in its System Information summary.  That seems quite different from the Intel Core i7-4810MQ that is installed.  

Highlights from the XML export:

    Driver
    Intel(R) Xeon(R) processor E3 - 1200 v3/4th Gen Core processor DRAM Controller - 0C04
    10.1.18121.8164
    0C04
  
  
    Driver
    Intel(R) Xeon(R) processor E3 - 1200 v3/4th Gen Core processor PCI Express x16 Controller - 0C01
    10.1.18121.8164
    0C01
  

I can also post the full output, if needed.

So is this a problem?  Or are these just generic drivers that covers a range of CPUs (and is the best option available)?

My other question would be whether I should keep Dell Command | Update, or just remove it and use SupportAssist exclusively.  Or the opposite?

Finally, if SupportAssist is the one to keep - which one of the two versions? (Or just remove and reinstall periodically when needed?)  I really dislike active services bloat.

• Dell SupportAssist v3.10.4.18
• SupportAssist v3.10.7.0

P.S. "DDVDataCollector" is the pits. I don't know what it does, and why it does it (and no-one seems willing to answer this!) but I know that it seems unneccessarily resource-hungry, and that Windows does not like it.  You'd think that if it was legitimate, Dell would have arranged with Microsoft for an exception to be included in Windows Defender by now.  Hence my urge to just eliminate SupportAssist entirely unless I have cause to use it.