BobF
Fire up Theme Editor and change the color of the Automation Read buttons to solid black for all states. 
Problem solved!!
 

I thought of that days ago, but it don't fix the problem... and how do In know  that down the road if I hit the wrong thing and mess up a track and it has something to do with the R being active. Like I said I don't get it because I don't need it, if I needed it I would know how to use it... it's not dumb to not learn what I don't need... I would just be a waste of my time... like this full post seems to be.. lol I done here! Carry on! :)

Dave000
and how do In know  that down the road if I hit the wrong thing and mess up a track and it has something to do with the R being active. 

 
Switch off the [R!] button in the Control Bar Mix Module. It bypasses all read automation in the project. I THINK it will solve your issue. I don't globally bypass automation read, so I can't be sure. 

Can't you just hide it using the Custom feature of the track header filter?

Reply to my own post: Unfortunately, I just noticed that the enable/bypass state doesn't get saved with the project. So the switch is automatically enabled again when you reopen the project. This behavior should probably be changed. Sorry that I couldn't help.

icontakt

Dave000
and how do In know  that down the road if I hit the wrong thing and mess up a track and it has something to do with the R being active. 

 
Switch off the [R!] button in the Control Bar Mix Module. It bypasses all read automation in the project. I THINK it will solve your issue. I don't globally bypass automation read, so I can't be sure. 

At this point, I'm honestly not sure what the actual "problem" is.  I just tried the global toggle and it does appear to work, but the buttons simply turn to greys instead of blues/whites.  Maybe that will do it for Dave.

Dave is being pedantic. There is nothing to fix because nothing is broken. No need for a workaround or a change in how CW have made the R button function. It is and always has been a useful feature. To think of it as a problem is an absurdity.   

Maybe we are all so experienced that we completely forgot about one potential automation-related problem that can easily happen to the OP or any new user who absolutely does not need automation.
 
Here's the scenario:
 

1. He accidentally/mistakenly clicks the Automation Lanes button on the track (this happens, doesn't it?). The Volume automation lane opens.
2. He wonders, "What's this?," and clicks the button again. The lane disappears. "Phew, what was that? Anyway, it's gone. No problem."
3. He continues working on the project and saves the project.
4. A few days later, he tries to adjust the track's volume fader in the Console view. The fader jumps back. "What's going on!!!"

 
IIRC, I've read in this forum that this (except step #2) actually happens to even an experienced user occasionally. Personally, I think clicking the Automation Lanes button for the first time should create a lane with a parameter-unassigned envelope which does nothing.
 
Anyway, I think none of the workarounds suggested in this thread can prevent the above potential problem from happening.