There
are algorithms which make use of
on-chip acceleration (
AES-NI is probably the most common on desktops), but that means additional chip real estate has to be sacrificed in the name of purpose-built hardware "blocks" (
example from Apple's current CPUs), real estate which is at a premium in a handheld mobile SoC. Modern mobile processors already have quite a few dedicated blocks for things like
SSL/TLS, JPEG, H.264, etc., because these are all things that people are expected to do on their phones A LOT as they browse the WWWeb, watch Netflix, and check their email (the battery life gains are deemed worth the extra die space), but I don't think that VPNs are common enough (on mobile, at least) for mfrs to go including additional specialized hardware to handle VPN coprocessor duties, at least not yet.
Plus there's a bit of a chicken-and-egg debate to solve as to
which VPN protocol is "the best" since that will have a strong bearing on which coprocessor(s) everyone decides to include, since if the overall standard ultimately ends up being something different than the block
your mfr included, then that device ends up with a power-sucking part of your chip that ultimately does nothing useful. As an example, Apple made a big deal about how quickly their iPhone 12 series could render 4K video "as fast as a desktop," but the reason it can do that is because
it shares the same media codec blocks as their desktop chips, so it is really those dedicated blocks doing the work SO LONG AS you are exporting your video in the format the media block understands (H.264 & H.265/HEVC
according to Wikipedia). If you try to export your video in some other format, then the chip can't lean on those blocks to do all that work, and so it will have to do it "by hand" (so to speak) and your phone will get a lot hotter...and your battery life will tank. So if the world suddenly decides it is going to move everything to H.266/UHEVC* because file sizes are drastically smaller or some junk, then all that fancy extra
single-purpose hardware is useless and suddenly the phone is "nowhere near as fast as it was." I frequently have to explain to people that the reason their 8yr-old Dell laptop suddenly can't stream video/do Zoom as fast as it used to or starts chewing through battery 3x faster after you ran that update is because Zoom probably changed their codec to use something newer than what's built into their laptop's built-in DX11-era iGPU or whatever, and the only way to fix that is to either revert the update (which might mean not being able to join meetings because outdated) or else it's finally time to buy a new computer.
--Patrick
*Not a real codec, at least as far as I know. Just a hypothetical example.