We started here  some discussions around the custom dashboards that come with Kiali.
Basically, the question of long term maintenance is on the table. There's a couple of dashboards that are currently outdated, wrt. the evolutions of the metrics in runtime frameworks. A suggestion is to try to find maintainers in the community, who use Kiali regularly enough and who run workloads with some of the given runtimes.
If no maintainers are found for a given runtime, perhaps the corresponding dashboard should be removed from Kiali operator.
I personally volunteer to maintain the vertx dashboards since I'm also a maintainer of vertx-micrometer-metrics.
Another option could be to reduce even more the scope of installed dashboards to keep only the ones strictly related to Kiali & service mesh (like Kiali+go, Envoy?)
Which brings another topic: be it in the short or long run, anyway, we will have "deprecated" dashboards (ie. not provided out of the box by Kiali operator anymore), we'll also have dashboards evolving with the versions of their target runtimes. What to do with the old dashboards? They can still be useful for people who are running old versions of runtimes. I think it could be interesting to create a repository to stockpile old / unsupported dashboards. Something like "kiali-custom-dashboards" ;
This repo would have no connection with Kiali operator, meaning that the operation has its own set of dashboards to install Kiali with by default. (or we could also imagine the operator picking a subset of dashboards directly from that repo; that could be a later step)