Note that there are archtectural limitations here that would not be trivial to overcome or to account for.
For example, the MB3 pop-up for View operations is built from a menu file, which means that you can edit it to control both the content of the normal pop-up menu as well as the radial pop-up, and there's even work being done to perhaps provide users with a means to edit these pop-ups using normal Customization tools, but ONLY for the View pop-up.
However, the MB3 pop-ups that you get when you've selected some feature or geometric object are not being created from a menu file that you could edit. Rather we have a single mechanism which reads the object highlighted and from this object itself, determines what options to include in both the MB3 pop-up as well as the radial pop-up. There are no menu files that are user editable, but rather the list of valid options are created on-the-fly, as it were. We chose this approach since it allows us to make changes to the global behavior of pop-up menus (including the radial pop-up) without having to go around and update literally dozens and dozens of menu files. This also allows us to add new object types, or update an existing object, and all we have to do is include, for this object only, the options that the developer wishes to be available from the pop-up menus, but these records are tied to the object type, not to the pop-up menu mechanism.
Anyway, I hope this gives you a better understanding of what this sort of enhancement would entail.
John R. Baker, P.E.
Product 'Evangelist'
NX Design
Siemens PLM Software Inc.
Cypress, CA