The goal: To understand why the system is recommending what it's recommending.
"Algorithm" is a short-hand for that goal.
Everything else is just clever wordplay to try and deflect the conversation.
I think it's the incorrect word. The "algorithm" requires a few pages of code. "Understanding why it's recommending" requires you get, and sift through, terabytes of user data from Youtube. They're very different.
How about we get Youtube to show us their algorithm and associated weights (assuming an ML-based approach, which is a huge assumption on your part) and then we can find out if that's true.
What more reasonable alternative do you see, with the existence of my personal recommendation feed? I'm not aware of any personal recommendation systems that don't use ML. Do you have any examples in mind?
Is user data, that's used to train, part of the process? I don't think so. It's an input to the algorithm. In the case of ML, the input is the only thing that matters.
Semantics, but I think it's incredibly important. It's the difference between posturing and actually affecting change.