The raytracing tag has... 0 watchers and 18 questions. Half of the questions don't have an accepted answer, and of those which do have an answer, the tag doesn't seem to add to or help filter the question:
Adaptative ray bounces in Cycles is a good question but the cycles tag seems to cover the raytracing aspect of the question.
Again, [cycles] seems to cover Why can't cycles cast one ray per image pixel, instead of rendering progressively to infinity? perfectly fine. While the argument that cycles is a very broad tag and raytracing narrows it, the rendering tag does just fine. It makes a lot of sense that if a post is tagged cycles and rendering, it's about raytracing. This makes [raytracing] superfluous in my mind.
What is branched path tracing and how is it useful? is a fantastic question but the cycles and rendering tags make the ray tracing tag unnecessary.
I think the rendering tag could substitute for raytracing here: Cycles light ray exiting the back of an object
Raytracing tag seems completely unnecessary for Boolean on cycles rays, not on mesh
Associating extra information to a ray in Cycles is probably the one question that does benefit from the tag.
The rest of the 9 answered questions are very similar.
To summarize, half of these questions never get answered and the ones that do just don't benefit from the tag. Raytracing seems to be a simple filler tag on bad questions and a useless afterthought on good questions. With those underwhelming credentials, it seems that it should be removed... Is removal a good idea?