hopefully not. Certainly it won’t be for you, because it’s pretty clear you are doing exactly what you say - mainly submitting PRs for bug fixes. Nice!
But there are real issues here. Just for a little history, it used to be VCV’s official policy that if an owner of a repo went “MIA” for a month that anyone cloud clone their repo and submit it to the VCV library, where it would be accepted. This policy created several flame posts from a developer, and was pretty visible.
At some point this policy was rescinded. I think it was when someone pointed out that it was in direct conflict with other VCV policies.
Now there are several (many?) cases of developers who have not (yet?) updated their modules to VCV 2. So some people are porting these to V2 and letting others knows that the enhanced versions can be found on the forked repos.
I believe that in some of these cases the original developers have no intention of ever releasing these ports. If there are cases like that, unlike your case(s), these people may be inadvertently violating both the wording of the license and the wishes of the original developers.
I don’t have that issue. When I decided to get out of the VCV module rat-race I announced it early, and explicitly gave a dev permission to port the modules, and even submit them back to the library.
For other devs who choose not to update, I can’t really say what their reasons may be.
In the case of this particular plugin, I guess we are waiting for @stoermelder to let us know what his plans are for his modules.