Maximum FTP Connections Limit Not Enforced Until Service Reload — Expected Behavior?

I'm reviewing the "Maximum connections" setting for the FTP server in WHM (Service Configuration > FTP Server) on a cPanel server running version 100 or later. My understanding is that this value is written into the vsftpd.conf template and only takes effect after the FTP service is reloaded or restarted.

The uncertainty I have is around the enforcement window: between changing the value in WHM and reloading the service, existing sessions appear to keep the old limit, and I want to confirm whether the new directive applies only to newly established connections or whether a reload forcibly drops active sessions. I also want to confirm the expected server response once the limit is actually reached — whether clients should consistently see a 550 reply, and where the rejection is logged (I believe /usr/local/cpanel/logs/access_log, but I'm not certain the FTP rejection events land there versus the vsftpd log).

Specifically:

1. Does the new maximum apply only to connections opened after the reload, leaving existing sessions untouched?
2. Is a 550 response the documented reply when the per-account limit is exceeded, and in which log is that event recorded?
3. Does the configured value reliably persist across vsftpd.conf template rebuilds in v100+?