There is pretty much no guarantee at all regarding what code a compiler will emit for bitfields. Per spec, the order and sizes can change.
The author does mention some of this but their conclusion is misguided: it’s not a portability problem, it’s a showstopper. Indeed, the next point release of the exact same compiler could very well decide to use a completely different behavior for bitfield.
Any seasoned low-level engineer would know: bitfields should never be used for register mapping, period. I wish the article made that more explicit.