Admittedly I'm likely to fall into your developer/advance user cagetories, and have some peculiar things I'm trying to do.
I have 2 connections, and I balance them with primary ipv4 on one and primary ipv6 on the other, with the alternate lines acting as backup for each. Utilising IPv6 on the unRAID server gives me ability to use both lines more readily.
I've dual stack IPv4+IPv6 at home currently on all equipment possible, but would like to progress towards IPv6 only. This has been covered as being done already by a bunch of companies within the Internet industry at various events such as UKNOF, NANOG etc.
Most large UK providers offer native IPv6 to all of their consumer connections nowadays so it's available for the majority of consumers who won't even necessarily know they're using IPv6 for a lot of things already. As IPv4 addresses get more expensive, the trend will be to either bury connections in more layers of NAT or use native IPv6 for true end to end connectivity. The double layers of IPv4 NAT involved in going from the internet to my docker applications isn't ideal.
As a compromise, how about enabling it in the kernel as a module, then if you really don't want it firing up to unwary folks, blacklist the module from loading which would suffice to protect those that don't want/know about it and those of us wanting IPv6 could simply unblacklist and configure manually as we need, rather than having to go through the hassle of building our own kernels each time unRAID kernel version bumps, purely to enable the IPv6 module.