UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.79 Safari/537.36

Steps to reproduce the problem:
Over in https://bugs.chromium.org/p/chromium/issues/detail?id=458552 there is an issue that needs the New Tab Page to be trying to show a Google Doodle. Unfortunately some days the region you are in may not have a Doodle and it's painful to try and get Chrome to show a Doodle in this circumstance. 

What is the expected behavior?
Command line switch to ALWAYS show a doodle.

What went wrong?
No such switch exists in a simple fashion.

Did this work before? N/A 

Chrome version: 61.0.3163.79  Channel: stable
OS Version: OS X 10.12.6
Flash Version: 

 While -google-doodle-url looks promising it is under documented (based off https://peter.sh/experiments/chromium-command-line-switches/#google-doodle-url ) because how does one know of an URL that will always return a Doodle?

After lots of searching I came across https://codereview.chromium.org/2660883002/patch/1/10009 which looked helpful but components/doodle/doodle_fetcher_unittest.cc
seems to have been removed from the repository at some point. Running
curl -H "Content-Type: application/json" 'https://www.google.com/async/ddljson?async=ntp:1&data_push_epoch=2000000004'
Just returns
{"ddljson":{}}
which doesn't tell you the structure of response when there is a Doodle. Searching more got me to https://cs.chromium.org/chromium/src/components/test/data/search_provider_logos/ddljson_desktop2.json?sq=package:chromium but copying that file locally and starting Chrome using
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --user-data-dir=/tmp/chromedatadir/ --google-doodle-url='http://localhost:8000/d.json'
Showed Chrome didn't even try and make a request to localhost:8000 .

The closet you can get is by going to https://www.google.com/doodles , finding a doodle active today, looking up what region that Doodle is active in and changing Chrome to use that region with --google-base-url .