No, you are not missing something, and Yes, this is a known issue.

The author of MooseX::InsideOut wrote it specifically to make it easier for Moose to inherit from non-Moose classes, we realized later on that it does not play well when inheriting from Moose classes. But as this was not part of the authors original requirements it hasn't been addressed. The reason for this issue goes deep into the MOP and how the accessors are set up vs. how the constructor does it's initialization. At this point fixing it is a matter of someone having the time available and the need for the feature.