This issue is caused by some invalid metadata in the "Fat" build of v2.3.3.0 of 0Harmony.dll. It looks like this dll is built with ILRepack, and it appears that ILRepack has incorrectly packed one of the type references - 01000126. If you open the dll with a tool like ILSpy, and look at the TypeReference metadata table for that type reference, you'll see it refers to an AssemblyReference that doesn't exist.
So in this case, Burst is "correctly" emitting an error message because of invalid metadata in this library.
I have tested with a locally-built "Fat" release build of Harmony, built from the latest code in the Harmony repo on GitHub (which is newer than v2.3.3.0). This works fine, so I suggest doing that as a workaround. You could also report it as a bug to Visual Scripting Enhancer, to ask them to update to the latest build of Harmony.