Sorry for misunderstanding.
To skip paying an expensive plan just for cookie bypass option, you will need to set nocache/private/expire headers for this pages on your origin. The situation is really the same as WP-Admin - the only difference is that you will need to do it manually, while for WP-Admin it’s by default. So list from above applies, especially 4. if you have spare rules available.
I don’t know your architecture configuration - proxies, loadbalancers, etc, but lets assume it’s simple config.
You can set it on a server level - nginx conf or apache vhost / htaccess.
Or built it within the theme or plugin. Function for this is nocache_headers() or you can apply a hook for more granular control over the headers.
In case you are using caching plugins, such as w3tc or super cache, you will need to tell them not to cache these pages (within own settings or code blocks), as they will overwrite the headers and cache the output anyway.
Business plan offers a railgun, which you can use for dynamic content when your visitors are logged in.