The integer stuff is actually improved in quite a few ways compared with the 48 series. Primarily, the integer can optionally have an assigned base, size, and signage.
Now what this means is that if you specify directly one of these optional values, that value will remain with the object. Changing the default base *will not* change the base setting for all hex objects.
If your home settings are in "binary" and you type #101, the calculator interprets what you typed as a binary value but does not lock it as "the user assigned this as a binary hex number". This is exactly like the 48. Typing #101b would flag "this is a binary number" and that one will then not change as your system setting changes.
Looking at your later posts, it seems you have seen this already. Provided you did not manually specify b o h or d on that hex number, whatever your default system setting is is how it will display. A list with { #10 #20 #30 } entered while in HEX mode will change its display as you change the home setting.
Carrying along information with each hex object has a lot of advantages, but does have the downside you've shown here of "well what if I just want everything to display in my current base". What would your recommended solution be given that it is important to keep the optional additional info for a hex object?
TW