No.You still seem to get the wording backwards. According to 1.0a section 9 you can always use content using any version of ogl independent of their outhorization status.
Section 9 says "Wizards or its designated Agents may publish updated versions of this License. You may use any authorized version of this License to copy, modify and distribute any Open Game Content originally distributed under any version of this License."
So section 9 does two things.
It gives WotC a permission to publish new licences.
And it gives licensees a permission to use those licences (which are, ipso facto, authorised licences) to use (in the indicated ways) OGC distributed under any version of the licence. Those versions must of necessity be authorised versions, because if not then they don't create OGC!
You seem to be assuming that authorisation is a variable property of a licence, analogous to how (say) being an employee is a variable property of a person (often they are, but maybe they retire or lose their job and so cease to be). But that's not correct. Authorisation is a constant property of a licence, that it enjoys in virtue of having been published as a licence by WotC (or its agent).
Material can be used under v 1.0/1.0a only if it is "OGC originally distributed under any version of the OGL v 1.0/1.0a".Hence defining 1.1 as authorized or not have no bearing on if you are allowed to use 1.1 material when you publish something under 1.0a lisence according to section 9.
And material that is licensed only under v 1.1 will not be "OGC originally distributed under a version of the OGL v 1.0/1.0a". The drafting of v 1.1 will ensure that. We've already seen one way it does this: it doesn't create OGC at all, but rather Licensed Content.
What you say about "the only way for 1.1 to call itself legally an "update"" isn't correct. WotC can publish a new licence and call it whatever they want. There is no legal restriction on this, other than general decency laws and bars on using protected public names (in Australia these are names to do with the Crown, the government, ANZACs and Don Bradman; I assume the US has similar sorts of protected names).However the "authorization" of the license you for your work when distributing/copying/modifying is of importance. Hence the only way for 1.1 to call it self legaly an "update" to ogl1.0a (which is a concept clearly in 1.0a section 9 what entails), which they do in the leak you suspect being a summary (despite containing the exact quots given in the Gizmodo leak) while preventing cross lisence use to 1.0a would be to either somehow revoke 1.0a (which would also prevent anyone including themselves to use 1.0a material as source, as section 9 would no longer be valid), or manipulate the meaning of the keyword "authorized" of 1.0a section 9.
"Authorised" is not a "keyword" - I've explained above, as well as in an earlier post upthread (#556, and see also my post #562) that it appears with its ordinary English meaning. And it does not need to be "manipulated". All WotC has to do is establish new contractual rights that do not intersect with the existing rights of licensees under the existing OGL. And I've explained how they can do this, pretty straightforwardly. The upshot is two ecosystems.