To be honest not really no.
But...
D3 is built around the selection object - exactly like jQuery. This presents some interesting capabilities.
For example you can have a big table and D3 will read the data from there. There is no need to duplicate the data, to sync them etc.
Furthermore the possibility to transform any random js example on the web in GWT java quickly, was a productivity boost.
That approach really paid off also for debugging. Consider the following case. D3 java does not work. What's the problem? Is it the bindings? Let's create a small example in js and run it natively. If it works it's the binding's fault. If it doesn't work then it is the way we use D3 or worse a D3 bug.
So I believe it was a pragmatic approach. We could use D3 docs, D3 examples etc.
Hope that helps.
Vassilis