HTTP profile and an ACCESS profile in the same virtual server for 11.x iRule

Access profiles are controlled by the Access Policy Manager (APM) module. If you have that module licensed and provisioned, you'll see options near the bottom of the virtual server properties page to set an access profile. APM profiles require an HTTP profile to also be applied.

By the way, you can actually skip the whole ACCESS::restrict_irule_events thing by moving your HTTP request logic to the ACCESS_ACL_ALLOWED event. It's mostly synonymous with HTTP_REQUEST but is triggered after access policy evaluation. Doing HTTP evaluation in the HTTP_REQUEST event with an acces profile applied can get dicey as the HTTP_REQUEST will get triggered before the access policy starts (and potentially disrupt the access policy processing), and after the access policy completes. The ACCESS::restrict_irule_events command allows you to see the HTTP events that happen inside policy evaluation, but that too can be dangerous depending on what you're trying to do.