As someone who has been writing JavaScript for 15 years and has never felt like writing it is a struggle I would ask... are they?
I don't know what it solves. Writing a language designed to be written by hand in another language and then transpiled to the first language you have to know in the first place to be any good at it has always seemed like a horrible non-solution. You don't know what you've actually written at that point.
Syntax, variable niceties are great too, of course, but do not define CS alone.
For me, it is the gray area, I am a language geek so the semantics of js are quite clear but js bytes me sometimes. In coffeescript, The syntax is better and the semantics are better exposed , so it may be a net win.
For a guy who is already familiar with coffeescript, the change will be likely negative. Familiarity with coffeescript is likely to generate bugs in javascript. You're moving from one language to another after all. The impact won't be huge as the two are quite close, but there is no reason to change in the first place.
Also, JS switch/case statements follow the good-old maldesign from C where each body has to end with break or it falls through.
Variable hoisting?
Getting rid of a dubious build step that doesn't get any real advantage in this project, but makes it slightly more obscure for people unfamiliar with CoffeeScript (and a lot of new developers don't bother to learn it now that ES6 is quite tolerable)?
It's a battle of philosophies. I value efficiency and just getting things built, so I love CoffeeScript. It's a breeze to read and write. OP wants control and customization, more 'freedom.'
If I was working on a team with OP and he instituted this, I would quit on the spot.
The constraints are minor, the gains of coffeescript quite clear. There is no important gains in sight that justify moving to js. So why changing ?
Changing for the sake of change, is silly and something all of us do. A successful project needs as much technical stability as feature stability.