If they didn’t want other use cases, they should have rethought the feature. The reality is that proxies came first. They see a LOT of use in reactive librarie

If they didn’t want other use cases, they should have rethought the feature. The reality is that proxies came first. They see a LOT of use in reactive libraries making it very likely that your classes get passed into one these proxies (and breaking if private fields are used). They knew all this when ramrodding it through over the many protestors warning about this and other things. The fault is 100% on the hubris of the spec committee.