Parts of the reason why I am writing/releasing these plugins is to explore various ways to do things - for fun.
One of my goals is to have plugins very easily configurable, including the possibility to disable/enable them via user settings - if possible without having to edit other files (like themes) which can not be done temporarily via a user command of the type view.settings().set("blah", "foo").... Rather than asking a plugin-developer to implement a given feature, I'd rather try to do it myself if I can. If someone backports a given feature to an original plugin, I feel vindicated!
While highlighting code remarks and "linting" are two distinct features, they share a common infrastructure (formating regions of code to have them stand out) which is why I integrating them in one plugin.
Another of my goal is to try to write very readable code [meaning no regular expressions if possible! ], so that others can adapt it easily. I still have some rewriting to do of the plugin as it exists but I am relatively happy with it (hence the public announcement). One thing I'm particularly happy with (others may not agree...) is the "automated" help feature.
As for specific improvement for your highlighter, I would need to take a closer look at the code. After spending a bit of time grokking the regular expression used, I decided to put it aside and just implement the functionality that I needed. I would need to have another look at what your plugin does to be able to comment more meaningfully - something I might be able to do later today.