I've dealt with someone like this before, but it was a full time job not a freelancer. So take what you can from our advice here:

TL;DR version: make them quantify why a certain technology/framework is bad for the project, not just the developer. Go to the boss and talk with them.

Put their feet to the fire, so to speak. If they try to claim a certain technology/framework isn't good, make them explain in quantifiable detail. What does that mean? I'll give you an example.

I had a job where we wrote vanilla PHP and JS a lot for an in-house application we were building. The team lead who was also the project manager felt that frameworks were too restrictive to be used. All frameworks. So we were stuck writing a lot of code that I felt was unnecessary. I came into the project half way and it was littered with near identical code, as if the idea of reuse was completely foreign. One day when I proposed we stop progress and take a week or two to convert to a framework, he again pushed back saying that they are too restrictive. I immediately fired back with, "How are they too restrictive?" He replied that they force you to do things their way. I kept pressing, "What frameworks have you looked at and what restrictions are you trying to avoid?". TL;DR, he never was able to justify it. All I got was "they just are". If they can't say "X technology uses a methodology that is counter-productive to the project's needs" then they are just being biased.

As for quoting time, he would tell our mutual boss that a given task could be completed in a week. I always felt his time was too short, and it wasn't until later I found out all his estimates were on a 50-60 hour work week. In the contract I signed with them, it said 40 hours. I got a lot of grief later for only putting in 40, they tried to guilt me and put a carrot on a string in front of me to get more hours. I hated working under those conditions.

My solution was to bring it up to our mutual boss. He would tell me to my face that he completely understands me, and he doesn't like what was being done. Sadly, I found out he was the kind of guy who would be sympathetic to you one-on-one but ignore you as soon as you walked out the door.

I left that job in search of better work, and the stress I no longer have is worth leaving a steady job.

I've dealt with someone like this before, but it was a full time job not a freelancer. So take what you can from our advice here:

Make them quantify why a certain technology/framework is bad for the project, not just them as a developer. As for the cost/quoting problem, go to the boss and talk with them about it privately.

If you are in a discussion as a group and they try to claim something isn't good, put their feet to the fire. Figuratively of course. If they try to claim a certain technology/framework isn't good, make them explain in detail. What does that mean? It means they have to provide objective reasons, such as "The routing method that framework A uses is counter-productive to what we are trying to accomplish." Not, "I don't like the way this framework structures their folders." Often times they will either back down or show they don't know what they are talking about.