That might require a lot of hurdle jumping most solutions require having root access on a device to do this. You could do it with Mx (Emdk or StageNow) to put the files in the proper locations but you'd need to find the relevant files to reconfigure the home screen. Note: The Android emulator is rooted by default so you can explore the file structure there.
Is there a reason they need to specifically use Chrome? Instead you could use something like Enterprise Browser (If you need APIs), Rho, or Phonegap to essentially create an application that is just a bookmark to the website they need. On Kit-Kat it will use the Chromium (same as Chrome) this way the page shouldn't change much if at all, but with Jelly Bean there might be noticeable differences depending on the webpage. With this method you can deploy the bookmark as a typical android application.
They have choosen chrome as their webapplication is using promises, which is not supported in the android build.
chrome version 42 is supporting promises by default.