I have an E6410 and "it works", VTd and all. I have 'trusted execution' disabled on my BIOS. I cannot remember if I did that to solve some problem or because my lack of knowledge about it. ALso my laptop also has some creepy intel vPro stuff. With my lack of knowledge about these issues, if I was truly paranoid, I would discard it, I guess. But for my everyday use and lack of funds, it works quite well :)
This crap on your screenshots looks somewhat familiar, less so from a few updates some months ago. I blame it on a buggy BIOS. It seems the video memory is not initialized on (re)boot. This can be a dangerous issue. Sometimes when waking up from sleep the background on the screensaver unlock dialog shows parts of the previous session (!!). Also when rebooting the computer you can get parts of the previous session instead of the noise on your screenshots. This background is just noise if you power it off and then on instead of rebooting.
In my case this dirty video memory happens only on the background, and the login dialog shows OK. When the session begins (when the whole screen is painted for the first time) this is not a problem anymore.
Another issue, which I guess is something KDE-specific: when
putting the laptop to sleep, the screensaver is not activated. So
when waking up the computer, there is no password prompt (!!!), and you get to your previous session.
This used to happen from time to time but now this is a consistent
behaviour. I usually try to remember to lock up the session
(control+alt+L) before hitting Fn+F1.
In addition, I have set up the HDD password and the BIOS password (both admin and user). But the E6410 BIOS is not requesting the password when waking from sleep. So, putting this all together, when the screensaver fails, opening the lid results in a ready-to-enjoy qubes session. KeepassX and all. Quite convenient for sure, but this means you'll have to do something beyond sleeping if you fear your backpack might be stolen. This issue really annoys me because I used to have a E4300 and it was consistent requesting the password(s) on waking up. Again, I suspect E6410 BIOS is both crappy and buggy :)