It is possible - no problem. You just need software which supports it. Restic does not but you could use workarounds e.g. mounting it with rclone mount --s3-version-at and restoring from there (it will be read only so you have to inject writeable locks directory - again you can use rclone combine and union remotes). Also restic does not support lock extensions - it is needed periodically to extend files lock as otherwise you lose protection for some older files making all lock setup useless. Again you can DYI it yourseld with aws CLI and simple bash script.
All together unfortunately means that unless you really understand what you are doing and are prepared to do some scripting forget about this solution with restic.
There is more details and chatter about this subject in this thread:
only true ransomware protection is provided by using compliance locking mode and all backup solution able to use it. In such mode nobody and nothing can delete data for as long as lock protects them. Only way is to terminate S3 account. So in case you try to play with it start with short lock and limited data until you iron your setup:)