Just to clarify something
The icons you see in the XMB are xml files from path dev_flash\vsh\resource\explore\xmb\*.xml
When the firmware boots it loads all the info from the xml's in memory, and since that point it doesnt matters if you change the xml on runtime because the real files are ignored. The only solution is to reload either:
-that specific "segment" inside the xml
-that xml file entirelly
-the whole xmb
By doing this the info about that xml in memory is "updated", and your change in the xml is displayed in XMB
The firmware have functions to do this kind of things, and are used in the official firmware, but are partially unknown, it seems to be made through:
xmb_plugin.sprx ---> XMB2 Interface ---> function 7
Mysis made a bunch of tests with it
https://www.psdevwiki.com/ps3/Xmb_plugin
And i made an experimental table with his tests (my table is a bit disaster, dont take it as facts)
https://www.psdevwiki.com/ps3/Talk:Xmb_plugin
My interest in that feature is because it allows to control the "cursor" (in other words, you can fake the dualshock outputs), and it allows to "navigate" the XMB
My idea was.... the backup managers that have an option named "direct boot" uses a method that is very incompatible (better dont use that feature)... but by controlling the cursor we could do this:
1)mount game
2)exit backup manager
3)automatize cursor to select the mounted game, and boot it (everything automatized)
In the practise this would make obsolete the old "direct boot" methods, and it would increase the compatibility of the new "direct boot" implementation to 100%
---------
Anyway... in the same way we can control the cursor, we can reload the XMB using something like that
The alternative solution to reload the XMB that seems to be considering the HEN devs is to take advantage of the "remote play" feature... just because when you enable remote play the XMB is unloaded... then loaded again
Technically is not a reload, but is pretty much the same, is just we know this is not "the good way" to do it, but it works, it was an idea from
@DeViL303 