When opting for an ‘extended gamut’ built-in monitor, you will have to accept that only correctly color-managed applications will show your pixels correctly.
Everything outside those color-managed applications will be blasting sRGB through a DCI-P3 panel, which means the colors will be over-saturated (even though the profiles are set correctly)
For example, external monitors usually have different ‘modes’ (the ones you pick with the on-monitor buttons), like sRGB, DCI-P3, etc. Laptops usually do not (which means you’re stuck with a DCI-P3 ‘mode’ forever). So an sRGB pixel of (1, 0, 0) will be output as ‘maximum power’ red on the DCI-P3 panel, on non-color-managed applications (such as some web-browsers, games, desktops, etc. etc.)
A lot of graphics software also, by default, exports sRGB colors, which means that one will always have to attach a monitor profile, and then convert to sRGB (hence my comment about extra friction)
And, if one gets tired of how sporadic good color-management is in software and decides to switch to full-sRGB workflow, one will find it’s barely possible. Setting the profile to sRGB will only make all colors to be over-saturated equally (which is likely better?)
Microsoft are working on it, but only a handful of systems support it, and it might introduce more problems that it will solve (ACM / Automatic Color Management):
There are ways around it, like
or
(But the former two will be at cost to performance, since they have to de-saturate the pixels through software (think ‘overlay’))
Hopefully this helps understanding the ‘issues’ around laptops with non-sRGB panels.