I wouldn't say there's no hope of a "fix" on the driver end since the code is open and anyone could modify it, but I understand the issue. 
These devices are a bit odd.
To get the repeat and the ability to stop it with a separate button action, I'd use one of two ideas. One is Rule Machine with a "Button" trigger--a separate rule for each button event. Create the repeat where you need it, then in the other rule (the one triggered on the button event that you want to stop the repeat), use a "Cancel Rule Timers" action and choose for it to act on the other rule. This is an option you'll see when using this option.
Usually I'd recommend a "Button Device" trigger in Rule Machine, but each "Actions" section (for each button event) is intended to be independent from the others, so you can't use a "Stop Repeat" action in one set of actions to affect an active repeat in another set of actions. That's why the above workaround is needed: separate rules, and you can call "Cancel Rule Timers" on the other rule. (Actually, I wonder whether you can use "Cancel Rule Timers" on the same button rule and have it work, but I haven't tested to see if that also affects only the current actions...). Alternatively, someone in this thread found a workaround using a local variable, which may also work:
If you haven't used repeats in Rule Machine before, there are are few threads about how to create various kinds of repeating actions. This is one of my favorites, despite the fact that it's ostensibly about repeated notifications--but the general idea of how to "stop" a repeat is the same regardless of what you actually put in the body of the repeat, so it's more broadly applicable than that:
(But again, the caveat that you need separate rules or the above workaround since you can't use "Stop Repeat" in the same rule/actions section is a difference from what you'll see in that post, given that you're working with different button events/actions sections or different rules entirely.)