I was with RaXPol (rapid-scan, mobile, polarimetric radar) yesterday with Howie B. and Jana H., and we capture tornadogenesis and relatively quick intensification from our first deployment location ~2 mi NE of the El Reno airport. As the tornado got to our SSW, we undeployed and later redeployed at I40 and Banner Rd. The radial velocity measurements within the tornado as it neared I40 were extreme. Fortunately for the people of El Reno, the tornado stayed in an extremely unpopulated area. As a consequence of this, however, there were an extremely limited number of Damage Indicators (DIs) that could be used to rate a violent tornado that were affected by the strongest winds in the tornado when it was near I40. I haven't seen the official survey results, but the extremely strong winds stayed, it appears, over open ranch and farm lands. Since the EF scale is a damage scale by it's very nature and design, I suspect the EF rating assigned to the tornado based upon damage will be significantly less than the EF rating associated with the peak winds within the tornado. This isn't uncommon, mind you, when significant tornadoes move through rural areas with little in the way of significant structures to damage. The winds on our lowest scans (0-2 degree elevation angle scans at a range of 4-5 km from the radar) seem to support a top-of-the-scale rating, but there needs to be supporting damage for it to be given such a "rare" rating. This is a conflicting consequence of a tornado staying away from population centers (good for the people, bad if one is trying to use damage and the EF scale as a proxy for tornado intensity)...
The El Reno multivortex tornado had a very large radius of maximum winds, was near an extremely strong RFD, and had very intense subvortices. I can guarantee it would have been catastrophic had it moved though El Reno or waited and moved through Yukon and the western OKC metro. This was a major league tornado.