I think they're saying that a setting that doesn't persist is a bug. It
could be a bug (Cakealk intended for the velocity bars to remain hidden if you decided to hide them, left the PRV, then returned - but they don't remain hidden) or it could be a design choice (Cakewalk figured that, like you, seeing velocity is something most users want, so they made it so you don't have to re-enable the bars every time you return to the PRV.)
I consider persistence more of a feature request. The basic issue is that default behavior is subjective,and some people will prefer one default behavior over another. The solution is either to have a preference (although they would add up quickly to a sea of preferences given all the possible default behaviors), or choose a default that the majority of users want.