Does that improve over having datatables contain only soft pointers (not loading the asset)?
Structs are broken on the asset / blueprint side, and Core Redirectors don’t work for them. Datatables can die after a small struct change and won’t let you edit their binary files to update them.
However, I found them useful. Haven’t used the asset registry yet.
In the past I used to have pointers within datatables to refer to other datatables. This grouped things together nicely. For example, I could map entries like “apple, pear, banana” to another entry “fruit”. This way I could specify the effects of eating a fruit just once (“add health by X”) just once and reuse that. That pointer could be soft, loading into memory only when required.