I'd only use it where it actually helps: If it's hard to visually keep track of what's happening without it. Otherwise it seems to add unnecessary visual complexity.
In a very large table, it does help track rows visually. I've found that, as long as this is justified, it is worth the initial step of "user possibly wants to click, finds out they can't" (reddish row has mouse pointer over it, sorry for all the blurring):
I find it to be less visually noisy than even/odd row coloring when there's a lot of information being presented:
The obvious downside to the highlighting, of course, is it doesn't do much good on pointerless devices (the pages above are very much intended for desktop use).
In your case, though, the highlighting doesn't seem functionally necessary imo.
As for sticking to material design guidelines, that's really up to you. I'm not a big fan of strict material design myself, way too much guessing and memorizing what icons mean because of its inexplicable quest to rid the world of text, and a bit heavy on whitespace. You can be somewhat flexible, the material design police won't bust your door down (yet), as long as your UI stays clear and sane.