The earlier answer to this question is wrong and shouldn't have been upvoted or accepted. exFAT isn't a flash file system. It's never used directly on "raw" flash. That would be horrendously inefficient, even if the cluster size matched the flash erase block size.
What actually happens is that exFAT runs on top of a block-device emulation layer, which is typically implemented in firmware on the flash device itself. Suppose the exFAT cluster size is 128K, the (fake) block device's sector size is 4K, and you write a 5K file to the exFAT volume. The exFAT driver allocates 128K for the file, but (ignoring metadata) it only writes 8K: the two sectors that actually contain file data. That's the same amount of data that would have been written if the cluster size was 4K. The difference is that if you write a bunch of 5K files, they will be separated by 30 unused fake sectors that are never read or written to. But that doesn't matter, because the real location where the data goes on the raw flash is unrelated to the sector numbers of the virtual block device. The exFAT cluster size probably has little effect on the amount of data written to the raw flash, or the number of block erase operations. When you include exFAT metadata overhead, larger clusters should be somewhat more efficient – but that has nothing to do with the size of the erase blocks of the raw flash, which is completely hidden by the emulation layer.
Of course, large clusters mean you run out of space on the fake block device if you try to store a lot of small files, and there's no way to coerce the emulation layer into letting you use the rest of the real space (short of using those sector numbers you skipped), so large clusters still seem like a bad idea. I don't know who at Microsoft decided that the default exFAT cluster size should be so large, or why, but I'll speculate.
exFAT has a much larger per-cluster overhead than NTFS: 65 times larger, in fact, because NTFS just has one bit per cluster for the free space bitmap, while exFAT has one bit in the bitmap plus 4 bytes in each of two FATs. On the other hand, NTFS has some significant other fixed overhead (notably, several megabytes for the journal), which is not directly tied to the number of clusters.
My guess is that they wanted exFAT to appear to have less overhead than NTFS. On small volumes, NTFS always consumes at least a couple of megabytes, so the 0.2% overhead of 4K clusters didn't seem so bad. But a freshly formatted 1TB volume would have about 2GB of exFAT metadata with 4K clusters, while NTFS would only need about 40MB. That would look bad (and would be bad, I suppose), so they had to use a much larger cluster size.