Actually, you misunderstood me. I know exactly how core storage works. I'm not arguing that the Intel 520 SSDs do or do not work. What I am saying is that in the case of a fusion drive on a MacbookPro 8,2, it doesn't matter what drives you use, they all will fail. In your post, you suggest that the issue could be either the motherboard or possibly the SSD being used. What I am saying is that it has nothing to do with the SSD being used as any LVG plugged into the MacbookPro 8,2 will fail, regardless of the drives being used. In my test cases, I used SSDs from Samsung, OCZ, OWC, and Corsair as well as regular HDDs (meaning that I used no SSDs, just two HDDs) and in all cases, the LVG will fail to load on the 8,2. In fact, in each case of a failure, I would put the drives into another Mac and they would work just fine, which is why I posted that the issue appears to be related specifically to this model.
With regards to your second point (using the command "diskutil cs create 'FUSION' disk0 disk1"), while your logic is correct there, it actually doesn't matter if you use "disk0 disk1" or if you use "disk0s2 disk1s2" in terms of the EFI partition. I wondered about that as well. Turns out that if you issue the command "diskutil cs create 'FUSION' disk0 disk1" and tail out the logs, what actually gets executed is:
1. Reformat and repartition of both drives
2. diskutil cs create 'FUSION' disk0s2 disk1s2
I found this to be the case if you run the command across 3 or more disks as well (disk2s2 followed by disk3s2, etc). Essentially, diskutil does not appear to allow for you to execute a core storage volume across multiple disks and wipe out the EFT boot partition.
Now, having said that, because of item number 1, if you executed this on a disk that has a Recovery Parition (not to be confused with the EFI boot partition), and you want to keep your recovery parition, then it makes a lot of sense to use "disk0" (where disk0 is the new SSD) and "disk1s2" (where disk1s2 is the partion on the second disk that you wish to use... make sure this partition isn't the recovery parition). When this is executed, the SSD is reformatted and only the partion selected on the HDD is formatted. Unfortunately, if your recovery parition is on the SSD (if your machine came with just SSD, no HDD), then you will loose the recovery partition if you attempted to make your own fusion drive. That setup is actually no supported and, when tried, creates a very unstable fusion drive setup. So, it's best to not do it that way.
Now, having said all of that, finally, please go back and re-read the original post from teooooo and keep it on topic. Unfortunately, this post is not about creating your own fusion drive. Rather, this post is about a problem that myself and teooooo have identified in that according to Apple, you can take a Mac that ships with a fusion drive from Apple (in both of our cases, a Mac Mini) and target disk mode that machine to another Mac running 10.8.2 or higher (in both of our cases, a MacbookPro8,2). According to the support documentation, this is supported and should work just fine. However, what myself and teooooo are pointing out is that is that it doesn't work with our MBPs. This has to be fixed by Apple because Apple says that it should work and it doesn't. In cases like myself, I use target disk mode to image new machines, recover data off machines, etc. If I cannot target disk mode new machines that come with Fusion Drives like Apple says, then Apple is on the hook to fix whatever issue is going on with the MacbookPro8,2 or give me a new machine that can (it isn't a warranty issue because it should work according to Apple).