Maybe I'm missing something...
> When designing precise UI-style layouts or pixel-aligned assets, pixels are a practical unit.
Except... the exact same slide, in the exact same window, will take up a different number of pixels when I drag the window between my MacBook Pro screen (254 ppi) and my Studio Display (218 ppi). Same window, same slide, but '96 px' is a different physical dimension.
Positioning something 100 pixels from the left side of the MacBook Pro screen will be in a different relative position from something positioned 100 pixels from the left side of the Studio Display.
How can pixels be practical when it varies based on the device you're using? Points are consistent.
If I have two objects on my slide and they are both positioned at x = 96 pt then I know they're aligned, no? Regardless of the display in use.
Arguably, points are more relevant than pixels. The slide layout is based on points (Inspector -> Document -> Slide Size), with a 'typical' slide being 1920 x 1080 points.
In Keynote, what's relevant is the relative dimension based on the slide size, so my 96 pt is exactly 10% of the overall width of the slide, regardless of the display density.
If your work truly demands 200+ PPI accuracy, then maybe Keynote isn't the right app.
> updating footers or colors across all layouts in a theme without having to open and adjust each individual layout. Keynote currently requires updating each master separately, which slows down larger projects.
That's true, but even then, changing a dozen slide layouts is easier than 100 individual slides. I'm just not sure how it would work from a user interface standpoint.
Note, though, that Keynote is substantially scriptable, so it may be possible to script a solution if this is enough of a headache for you.