Sometimes “brilliant” in the same sense as flaming wreckage, it seems.
Sadly, what you report is the same result that I get for a fresh project in 6M62. The test project I was using before had some other stuff in it, including a different kind of value not attached to a nameless property, and this changed the required offset.
Because the routines for printing the specific values (e.g. E67()) are related to the order of declaration of the kinds of values, and because not every kind of value is necessarily used as the basis of a property, a single fixed-size offset will always be unreliable in the general case. (A kind of value not used as a property can be declared between two others that are used as properties, so for the two used as properties the first would use offset N but the second N+1.)
As @Draconis put it a few years back (see Programatically printing all properties associated with object?), this attempt was “definitely hubris.”
Perhaps somewhere in the compiler code there are secret calls that can be used to get at these hidden kind ID values.