All those points can improve Data Unit size and subsequently consolidation and reporting performance, and those points should be carefully considered and incorporated at design & initial build time. Some of those items are rather hard to fix after the fact.
Your list doesn't mention splitting data into additional cubes. Things like allocation rates or factors as an example, do not need to be stored in the cubes that consolidate up the entity hierarchy.
Another item not on your list is to ensure calculations do not retain unnecessary detail. For example, when computing let's say YTD-NI in the BS, you can usually strip off all UD detail, and sometimes even IC detail too, as users can drill back to that detail if they need to see it. This can strip out a shocking percentage of data.