As far as I know, Pixels are the only ones that allow resigning the boot loader chain with your own OS though :/
This prevents all kinds of attacks where people could push things onto your phones OS. In desktop world, this is known as "secure boot".
Many devices will, however, only accept OS signed by their manufacturer - e.g. Apple iPhones/iPads will only boot an OS signed by Apple and noone else. This is why you can't ever run Linux on an iPhone or iPad.
In Android world, many manufacturers allow users to disable this verification (known as "bootloader unlock"). This allows running of non-manufacturer provided OSes (e.g. LineageOS, GrapheneOS, etc.). However, except for Pixels, they don't allow you to supply your own signing key to the bootloader, so you lose the security benefits of the secure boot chain and open yourself to big set of security attacks against your phone.
On a Pixel (at least some of them), you can provide your own signing key and reenable secure boot when installing another OS.
Link to the original announcement: https://calyxos.org/news/2022/04/01/fairphone4-oneplus8t-one...
Link to the feature removal by OnePlus: https://calyxos.org/news/2022/07/06/oneplus-android-12-reloc...
Curiously enough this feature does seem to available for the fairphone 4 too!
GrapheneOS never tried implementing this for OnePlus or FairPhone because it's not the only reason they stick with Pixels. The Titan security chip offers other benefits they want.
Not with a kernel that wasn't provided by the manufacturer you can't. This massively constrains your options. I can pull a Debian or Ubuntu image off their website and install it on any old laptop, but for phones you need an image specifically tailored to each device, and it'll only get kernel updates as long as the manufacturer continues to provide them since they're all bespoke kernel forks per-device.
But I of course agree with the overall point, that no interaction with the company should be necessary just to update the OS.