Also, when I lived in France, it was a matter of a phonecall to Dell to get a US qwerty keyboard instead of azerty. No problem at all. I think a colleague asked for an 'English' keyboard and got a UK qwerty, that's the only thing to be wary of.
Yeah, I‘ve seen that Dell for example sells US BTO options in the Netherlands, but in the past (when I considered an XPS 13), dell.nl didn‘t ship to Germany. But obviously the times have changed, and it‘s much easier today to get US keyboards than 10 or 20 years ago.
Real Dutch keyboard layouts never took off unlike what happened in France and Germany. We're not that dependant on our diacritic characters (although I am a stickler for correct usage).
Personally, I prefer the standard US layout, because I use more than one language. For Dutch („éë耔), English (“—”), and German („ßöüä”) the compose key does everything I need and more. For Japanese there is a dedicated IME (Anthy).
On Windows, I use WinCompose[1], which works decently well.
[1] https://github.com/samhocevar/wincompose (Trivia: WinCompose was originally written in AutoHotkey!)
Instead of having to type <Compose ' o> for a ó, I just type <AltGr+o> (or alternatively, <AltGr+' o>, and similarly <AltGr+` o> for a ò)
I can't stand those weird alt-codes Windows users end up memorizing. You only know those characters for which you've learned the codes. With the compose-key, you can guess anything that is diacritic character, and lots more besides¹.
I showed a colleague on a Windows computer WinCompose when she got wanted to be able to easily type a number of special characters (like en- and em-dash) without having to hunt for them in a character map or remember arcane alt-codes. She's not a developer, but it clicked instantly. Just think of a logical sequence, and get the character you want (for en- and em-dash its [compose - - .] and [compose - - -], respectively).
1: Like superscript numbers. Once you know that [compose ^ 1] yields ¹, you know ²³⁴⁵⁶⁷⁸⁹⁰ too.