Well, I think the SSD part of the FD will always leave some space for catching the writes. Then reading the file afterwards, you will always hit the SSD part. So writing a gig or two, reading it again and deleting it may not be a suitable benchmark here.
In real life, you read data from all* places, the SSD will miss, and you get the full performance hit of the HDD.
I don't know exactly what is put on the disk and how much it will shuffle data around. My guess is it favors heavily accessed files, small files, recently used files, and works as a write buffer (which is in line with the recently used files).
* Or you might mostly do the very same tasks, and the SSD has everything cached for you. Which is the use case the manufacturer likes to see.