DHCP v6 exists not to coddle or comfort admins used to a v4 world. DHCP v6 was added because v6 will /Never/ be adopted without it. Ever. Full stop. DHCP facilitates two-way communication prior to address assignment and lends flexibility to deployments that are now considered indispensable.
Having waded through the mega-thread with Lorenzo (who I've met by the way and he is a top class guy), this appears to be the nub of the dispute. It's some kind of immovable object/irresistible force situation.
The Android team build what is primarily a consumer product. When they make decisions, they think in terms of what is best for ordinary consumers. They also consider the needs of software developers. Therefore they highly prise qualities like "it just works" and "my apps don't break" and "I can tether without restriction". From this perspective as far as I can tell, Lorenzo's position is 100% correct. The founding vision of IPv6 was that you should always have as many addresses as you need for whatever purpose, and we should never need bizarre technical hacks to work around a lack of addresses ever again.
The network admins on that thread are building what they perceive as a 'take it or leave it' service, often, provided to a captive audience like a university campus or enterprise. Therefore they highly value qualities like "I can satisfy the legal department" and "I can use my existing hardware that only supports feature X" and "I can block tethering to my network to implement some security policy". They care relatively little about user or developer experience, as evidence by the number of comments on the thread of the form "If we can't get our way we'll just ban all Android devices" or "The device should tell the user that 464xlat is unavailable and let apps break" or "the device should tell the user that tethering is forbidden". They care little about application reliability or complexity as long as they can tick some boxes at the end of the day and satisfy various policies. From their perspective Android is just making their jobs harder and Lorenzo is therefore being mind-numbingly unreasonable.
This situation is somewhat confused and hard to distill because there seem to be multiple different things being discussed on the same thread, e.g. DHCPv6 PD which is apparently unrelated to address allocation.
Now, frankly, having read and understood many of these comments, I find myself siding (weakly) with Lorenzo, and not just because I know him. As an Android user and an app developer, my priorities are more closely aligned with that of the Android team. I do not wish to experience apps breaking or "tethering denied" messages in future due to some lawyer buttcovering that was translated into a network setup with the absolute minimum of effort by a monopolist IT department. If that means I fall back to IPv4 for a while instead, well, so be it. If that means my phone cannot reach the small number of IPv6 only networks when connected to some random university campus, OK, I'll use my LTE connection. And then I'll complain to the IT office and tell them "just buy an iPhone" is not an acceptable answer, so they had better get on it and allow my device to grab as many devices as it wants without having to go through a DHCPv6 server. Just like my home and mobile ISPs do. And if that means they have to do more work to satisfy the next BSA audit - well, that's why they get paid the big bucks.