I had expected this story to tell me that different battery chemistries react differently to different drain patterns, ie that low-drain usage might be better served by battery chemistry X and spiky high-drain usage by battery chemistry Y, and the OS could switch the power source between the batteries depending on the predicted near-future discharge pattern, based on what app was foregrounded or whatever.
But the idea that your battery would benefit by knowing your flight schedule seems to be reaching pretty far for a justification.
BMS in a laptop mostly just has to keep the battery safe and avoid unnecessary charge/discharge cycles. In a more complex system trying to salvage every joule of energy and maximize lifespan of each cell, the fact that batteries are less efficient to charge (or discharge) the closer they are to full (or empty) might be taken into account when deciding which to charge/discharge (for example).
A car might dump sudden regenerative braking power into high-C batteries if the main batteries can't take that charge at a given instant.
Satellites often use exotic batteries able to fully charge and discharge 10 times a day for decades at a time, but these have enormous self-discharge rates measured in days. Every chemistry has a unique set of compromises. There is plenty of room for smarter BMS in consumer systems that manage complex battery storage arrays responding to thermal, aging, cycle count, charge and load pressures more intelligently.