That is not entirely accurate. You cannot lump everything together like that, as it isn't "the developer" allocating inventory to everything. While the II inventory may be based upon estimates for demand, the MVC Trust inventory isn't based upon estimates for demand.
The Trust owns its Component weeks. When additional weeks (not owned by the Trust) are added to the MVC Trust inventory for usage it is done because of the Exchange Agreement; meaning an enrolled deeded owner, say in Spain or Aruba, elects Club Points in lieu of inventory, and thus the Spain or Aruba week becomes part of the MVC Trust Exchange Inventory for the particular use year. The developer doesn't randomly allocate Aruba or Spain inventory when the developer doesn't own that inventory. Sure, if the developer has inventory for sale at a location, it can do with it what it wants (rent, exchange, deposit to II, use for promotions, opt for BonVoy points), but that is only for developer owned inventory.
Just like the VSN inventory. Each location has its owners with either weeks or HomeOptions (excluding the two different Flex Programs). Using Nanea as an example, it isn't randomly allocated inventory to the Nanea HomeOptions inventory; it is the entire pool of HomeOptions inventory (leaving aside the one building that was sold to the Westin Flex). If none of the Nanea HomeOptions owners elect Club Points, there isn't any Nanea inventory in the MVC Trust pool. If every Nanea HomeOptions owner booked his/her ownership, then there isn't any VSN Nanea inventory bookable with StarOptions at 8 months.