Though they don't use the batching method outlined in the video - it would be interesting to see PBRT modified to do it and compare the resulting efficiency in rendering.
Ptex really chokes with non-coherant texture accesses (partly due to the anisotropic filtering method it uses) in terms of thread scalability, so Disney have gone to great lengths to get around this issue. Doing such accurate texture filtering (the same goes for standard UV EWA filtering) is technically better, but is expensive, especially in a path-tracing context, where the whole point is to amortise the cost of shading over all the rays by making each intersection / shading calculation as cheap as possible.
From what I hear there are big downsides to this current implementation: the streaming of batches is pretty much off-line, so time till "first pixel" is significant, and thus you don't get interactive rendering functionality.
You are right though that it would be fascinating to see the speed difference. My guess is that it would be substantial.
Even compiling PBRT with Intel C++ instead of Microsoft's C++ compiler gives a %30 - %50 speedup, likely due to reordering instructions for better memory coherency on a granular level (batching rays would give better memory coherency on a very broad level).
They've added other cool new stuff too, such as volumetric path tracing, progressive photon mapping, hair (bezier curves with a Kaijya-Kay BSDF) and a Photon Beam Diffusion BSSRDF.
http://www.disneyanimation.com/technology/innovations/hyperi...
If you want to learn more about rendering then here is some more info:
Stanford CS348b course notes:
http://candela.stanford.edu/cs348b/doku.php
Cornell CS6630 course notes:
http://www.cs.cornell.edu/Courses/cs6630/2012sp/schedule.stm
Eric Veach's Phd thesis:
http://graphics.stanford.edu/papers/veach_thesis/
Physically Based Rendering: From Theory to Implementation by Matt Pharr, Greg Humphreys and Wenzel Jakob (book and open source implementation of a state of the art renderer):
http://pbrt.org/