Different cache bin for tokens

Using custom module cache bins is discouraged, I don't understand why this is needed. There are only few token cache bins but they can be very large, so it's not a good fit for something like cache_bootstrap.

Custom bins allow for fine-grained control over caching for a module's data, ensuring optimal performance and minimal cache conflicts.

Benefits of custom cache bins include isolation, allowing for the separation of cached data related to a module from other modules, and control over how data is cached, retrieved, and invalidated. Custom cache bins also allow for optimization of caching for a module's specific use cases, improving performance.

When implementing a custom cache bin, it's important to consider factors such as cache granularity, data validity, and cache-clearing strategies. Custom cache bins are a powerful tool for fine-tuning caching mechanisms in Drupal.

#7 sounds like a ChatGPT explanation to me.

There is no need to have a cache bin for every little bin, Drupal 8+ optimized for fewer, semantic cache bins instead of basically having one for every module.

Also, this is just the tree cache, which is only used when displaying token UI, the actual tokens are cached in cache_default and that's defined in core.