Yes, but with stapling only the web server connects to the OCSP server. It then caches the response and serves it directly to clients. So with OCSP stapling there's no reason for the user's client to ever connect to Let's Encrypt's servers.
Edit: note that you shouldn't rely on this. If OCSP stapling fails (i.e. connection failure, DNS timeout) then your server might just not send a stapled response, and the client could do its own lookup. So you shouldn't assume that enabling OCSP = no client will ever do its own OCSP lookup. Stapling is primarily an optimization to reduce latency for clients that do revocation checking.
When you use an HTTPS web site or other TLS service with a Let’s Encrypt certificate, your browser (or TLS client) may query Let’s Encrypt to check whether the certificate has been revoked (“OCSP request”). If your browser makes an OCSP request, our servers will automatically record your IP address, browser, and operating system in temporary server log files. We do not use data from OCSP requests to build profiles or identify individuals. Temporary server logs are used for operational purposes only and are normally deleted in less than seven days. We may retain a subset of server logs for longer periods in order to investigate software failures or abuse. If we do so, we will delete any stored logs when we are done investigating. We may also compute, retain and publish aggregate information from server logs, such as which certificates generate the largest volume of requests. We will always strive to ensure that such datasets do not contain information about the activities of identifiable users or devices.
...and this part is pretty important. @kleingeld, if you configure your server to use OCSP stapling, there's no reason any of your users would be sending OCSP status queries--because you'd be providing them along with the cert.