Clock speed matters with OVPN - mostly due to the context shift between kernel and userland (OVPN is a userland app, but the tunnel driver is kernel space).
Probably a good reason why Intel J1900/J1800's are popular with many of the OpenVPN crowd - they're not the stoutest processors (compared to other x86), but they're clocked fairly fast at 2.4/2.53 GHz respectively on turbo clocks - which definitely helps with the userland/kernel jumps...
Going with Airmont - Braswell does offer AES-NI, which is always appreciated over Silvermont on Baytrail-D (which doesn't have AES-NI) - with OVPN, J1800 still wins over N3700 at high bandwidths - depends on the configs, but generally...
That's why I mentioned Core-i3 - there are a couple of chips there that are close to i7 on single core performance, and OVPN will definitely win - higher clocks, and Core-i3 also does AES-NI for Ivy and later...
Clocks are also the reason why many over in the AsusWRT community do try to overclock there - the broadcom SoC's are a bit compute bound on the OpenSSL side, but more of a problem with context switching and memory performance - and there, overclocking helps more on the mem and context switches..
My preference has always been l2tp/ipsec - mostly because we don't have to do the kernel/userland jump, so it's more efficient, but even there - it will leverage CPU features and clock/mem speeds...