I am running the WWDC build here as well.
It is not noticeably WAY faster than Leopard in daily use and I abused it a lot especially with external and network drives, it's just a tiny bit more stable and responsive but it is definitely not way faster than Leopard's Finder. We're talking less than 10% better performance than what people are assuming with 50% or more.
Now my experience may be different for majority of people with HDs because I have an SSD in my system, so it is possible that Finder is actually much more responsive and faster on hard drives but actually it may not have a big difference on SSDs.
Thus the wording in my previous post was "may not be faster" which is not the same as not "definitely won't be faster".
Also my WWDC build is only running in 32bit, 64bit mode of SL refused to run on my early 08' MBP 17" which is definitely 64bit at 2.5Ghz Penyrn. I bet the majority of people is not running it in 64bit mode either.
BTW rewriting an application from Carbon to Cocoa doesn't necessary means that it'll be faster, more responsive and better overall. A bad code is bad code regardless of what API it uses. In this case, Apple probably didn't just simply just convert it from Carbon to Cocoa, they also refactored and optimize the code to take advantage of GDC in the most efficient ways.