The same applies with a high chance to Manticore as well and tus the service in question is currently correctly detected as a MySQL service.
From a vulnerability test perspective the service indeed could be detected as a Manticore service so that MySQL tests working on a version of MySQL are not running against / reporting for an unaffected different product.
This could be handled for Manticore in a similar way then sw_sphinxsearch_detect.nasl / mysql_version.nasl for Sphinx.
I will create an internal task for this improvement but (unfortunately) don’t see that this will be done anytime soon so the following would be required:
Some community contributions on this topic
Creating overrides for the MySQL results on the system in question until the improvement have been made