[sk83]

According to Peak3D it doesn't do anything:

https://github.com/xbmc/xbmc/pull/16929

m_formatname is only for display in Kodi codec info OSD, IMO hevc is more common then h265

I concur. As far as I can tell it's the mimetype that decides which decoder will be used. "video/dolby-vision" results in codec OMX.Nvidia.DOVI.decode being used no matter which string(including gibberish) is used for m_formatname.

@MrMagic:
Here's a Matrix build with the advancedsettings functionality:
https://ufile.io/76xbe039
Identifier "org.xbmc.kodi19dv", label/name "Kodi 19 DV"

As @fandangos stated, the m_formatname doesn't matter, but maybe some experimenting with the timeout values will help. It also logs(for matroska files) the DV profile, level and other info, which may help in pinpointing which DV streams makes the decoder go bad.