Insufficient data; depends on details of intersection, traffic, drivers, timings, etc.
Also “spent waiting for the light to change” is not well-defined. It’s not a computer circuit, so many things involve significant delays.
For just one example, the more often the lights change, the more often people need to spend time slowing down to a stop, and speeding up from a stop.
So, in a symmetrical situation, the time spent moving in any direction is always less than 50%, because of the time needed to slow, stop, wait, and speed back up.
The only way to really tell, for each intersection and traffic situation, is to record what actually happens there. Also because even the amount of traffic trying to use an intersection is generally not predictable, and depends on everything happening all around it, even a long way away. One closed freeway ten miles away could have major effects on an intersection. And again when that freeway re-opens and releases a glut of cars.
But there will be some time where cars are traveling, and some time when cars are stopped, and some time when cars are not going full speed because they were stopped before (and the time to get up to speed again typically evolves each car waiting for the one ahead of it to notice and get moving again).
As for cars turning right, they typically slow down a little to do so, but they also remove themselves from the traffic you’re measuring. Net effect is good, even without considering that a 4-way intersection that didn’t let cars turn right would be preposterously dysfunctional.
Turning lanes help reduce the impact of turning cars on traffic flow.