Depends upon your point of view.
Since 2015, I've never even considered leaving an "empty" path on any docker template and instead of simply deleted the path from the template.
With 6.12.8, docker is now enforcing a specification and returning an error if you left an empty path on a template when installing it or updating it. Since there is already a number of users with this issue (self-caused), the plugin is changing how the docker run command gets generated to ignore this problem.
There is NO bug with the OS. There is NO bug with docker. The plugin lowers support requests in the forum on what the issue is when all of a sudden they update their containers and they disappear.
You don't need the plugin if you have no templates with empty paths and always delete any empty paths on new installations from CA.