Yes that is exactly what is happening to me as well. I removed the Isolated attribute from the class level which solved the ForceIniitializeFackeLogProvider error but then I also started getting the AAAScopes.VBRecordScope error. I will definitely let you know if this gets resolved as it renders the product usesless.
The funny thing is, in all of their documentation it does NOT tell you that you need to reference the AAA .dll, just the TypeMock Core and VisualBasic .dll's. So pretty much right out of the box this is broken for me. Frustrating.