Hi,
SMB is a client/server Model, so I don't think client can force it. It's the SMB Server setting that can force encryption and the client must support it.
Encryption is provided by the 'Protocol/SMB3.0' itself (@Session/share level), It can either be for all the shares or at individual share. Therefore, whatever Ontap version supports SMB3.0 dialect, you should be able to enable it.
By default, it is disabled (b'cos of possible performance impact).
ONTAP (SMB Server): You can configure the desired SMB encryption setting on a share-by-share basis through a share property setting or at SVM level for all the shares.
SMB Client: To create an encrypted SMB session, the SMB client must support SMB encryption. Windows clients starting with Windows Server 2012 and Windows 8 support SMB encryption. SMB clients that do not support encryption cannot connect to a SMB server or share that requires encryption.
I think it's worth testing to see if there is any serge in CPU at client or storage side due to it, I haven't used it so I can't share first hand experience with you. Following section do talk about it:
When SMB sessions use SMB encryption, all SMB communications to and from Windows clients experience a performance impact, which affects both the clients and the server.
Performance impact of SMB encryption:
https://docs.netapp.com/ontap-9/index.jsp?topic=%2Fcom.netapp.doc.cdot-famg-cifs%2FGUID-EF158266-85EE-4648-8D0F-6F80F0E13DCA.html
SMB is well documented in Microsoft docs as well, so testing is worth it.
Thanks!