Some of them yes, such as:
There are a few more, which randomly delete keys, but I kinda gave up at reporting them, since one got cleaned up into obscure TODO no one will check again, and other one was not reproduced despite being very easy to reproduce.
The three main bugs that are currently most dangerous are:
1, Removing some of the keymap input entries will result to some others removed on keymap re-import.
2, Some keymap entries are order dependent, but the keymap editor has no means of reordering the entires.
3, When you create key binding of same operator mapped to same hotkey, as soon as you do, both new and original keybinding will disappear, destructively, without any way to undo, so you have to roll back to last saved exported map.
Here’s an example of #1,
If you delete some of the keymap entries using the [X] button, then proceed to export the map, and then reimport it again, it will actually delete quite a few more entries which were assigned to same/similar operator, but different keys. If you click restore, you will gain those key mappings back, BUT if you do not notice it, even once, and proceed to export the keymap again, those key bindings will get deleted forever.
So all it takes is to forget it even just once, and you may lose up to hours of work, by having a keymap that’s missing many of the keybindings because you’ve deleted some of the remotely related ones.
EDIT: Forgot breaking bug #4
If you export keymap with nothing in the viewport selected, there is a random chance that the properties of set object mode operator in object non-modal categories will get wiped, effectively disabling those key bindings:
So I have to periodically re-set them save again and hope they stick.