Many storage devices out there can take a pool of storage and present space either via block level protcols (FCP, SCSI, iSCSI) as LUNs or via file level protocols (CIFS or NFS) as file shares. If you are currently presenting a LUN to an MSCS cluster, and the Cluster is in turn presenting shares via CIFS, then at a very high level it is likely possible that you could migrate the data internally on your storage device and present it as CIFS shares to windows hosts (you can generally present a slice as a LUN or a share, but not both for a given allocated piece of storage. Some kind of interally rearrangement of data will likely be required, and probably some vendor services).
MS basically defines the shape of the CIFS standards As new service packs and OS versions come out, now features are continually added. There's generally a lag between when MS releases a feature and when storage vendors add that feature to their products. If you need the latest and greatest features, you'd be better off presenting LUNs to a Windows file server or clustered file server.
Why was it a cluster? If the intent was to provide HA, then does the storage provide the same or better HA? If not, you may consider staying with an MS cluster.
How much does the CIFS license cost on the storage device? Generally it isn't free. Have you done a cost/benefit analysis?
In the end, depending on your specific requirements and the results of your cost/benefit analisys, it could go either way. If you do stay with LUNs presented to a clustered windows file server, migrating is easy. Evict a node, add a new node, rinse and repeat for the other node. The old rolling update.
Just out of curiosity, what is the storage platform?