So when a client requires something, one delivers it. If in one's professional opinion one believes something else would serve the client's goals better, one runs it by the client. Usually they will be ecstatic with the designer's insight, as we both agree that designers are the enlightened experts here. However, sometimes the client will not like the idea, so one just knuckles down and gets on with it.
So it seems that it is you who is actually confused on this point. However when you graduate from Lancaster University, pass over from the world of academic pontification, and into the world of commercial reality, I am sure you will experience lucidity.
I'm not going to argue further though, because apparently you're incapable of arguing your point without condescending remarks.
If a client requires a copy of another site, then no, his requirements don't supplant everything. If you know exactly what you want, you don't need a designer, and hiring one will just piss both of you off.
A 'designer' by definition is someone who designs — comes up with a plan — not someone who implements (which is completely secondary). And frankly, the designer is the expert here, not the client. So all a client should do is fill the brief, and give specific feedback when asked (not say things like "I like that logo because it looks fresh"). That's it.
The client should trust the designer to make the right decisions based on his requirements. And going on the same note, a good designer will ask the right questions and pull a client's requirements out of him. This, you're right about, yes. But clients WANT to guide the designer, so YOU might not want to hold hands all day, but most clients do, and that's why we reach the situation in the first paragraph : http://theoatmeal.com/comics/design_hell
This post is from the point-of-view of a designer, so the client is (obviously) the bad guy. I'm not defending either; just stating why your comment is wrong.