This is a four year old thread but I believe (as per prior industry standards) the conclusion/solution offered is inadequate and wrong-minded.
This is what profiles are for. Cloud backup and storage in typical computing scenarios use profiles in support of applications which offer multi-seat licensing. This is critical to users who wish to use some number of headsets on the same local area network for shared experiences such as:
Enjoying movies together with family and friends,
Collaborative content creation,
Roundtable business meetings,
Corporate customer local presentations,
Games such as "The Two Of Us" or "Portal 2"
etcetera...
If profiles rather than Meta Accounts were used then each application developer would have the choice of offering multi-seat licensing. Account owners acting then as an Admin, could also more easily administrate updates, account control, permissions, and so forth - as per established standardized computing.
Forcing Meta Account partitioning on these scenarios is also disadvantageous and more costly for Meta formally TheFacebook, Inc., considering both account maintenance and data center server load. Additionally, for those concerned with green ecology, using profile rather than account partitioning would reduce electrical consumption for every participating end user as well as within the data center. The (costly) power savings are assumed to be enormous without specific calculation on privately available logging data.
For your consideration...