Laravel バリデーションでのSoftDelete(論理削除)とUnique制約の最適解

Schema::table('Users', function (Blueprint $table) {
            $table->id();
            $table->string('email')->unique();
            $table->softDeletes();
});

<?php

namespace App\Models;

use Illuminate\Contracts\Auth\MustVerifyEmail;
use Illuminate\Database\Eloquent\Factories\HasFactory;
use Illuminate\Foundation\Auth\User as Authenticatable;
use Illuminate\Database\Eloquent\SoftDeletes;
use Illuminate\Notifications\Notifiable;
use Laravel\Sanctum\HasApiTokens;

class User extends Authenticatable
{
    use HasApiTokens, HasFactory, Notifiable;
    use SoftDeletes;
    
    protected $fillable = [
        'name',
        'email',
        'password',
    ];

    protected $hidden = [
        'password',
        'remember_token',
    ];

    protected $casts = [
        'email_verified_at' => 'datetime',
    ];

}

public function rules()
{
   return [
      'email' => 'unique:users'
   ];
}

<?php

namespace App\Rules;

use Closure;
use Illuminate\Contracts\Validation\ValidationRule;

class EmailUnique implements ValidationRule
{
    protected int $user_id;

    public function __construct(int $user_id)
    {
        $this->user_id = $user_id;
    }

    public function validate(string $attribute, mixed $value, Closure $fail): void
    {

        $object = User::where('email' , '=' ,  $value)->whereNot('user_id' , $this->user_id ?? null)->first();

        if(empty($object) === false){
            $fail(__('メールアドレスはすでに登録されています。'));
        }

    }

    public function rules(): array
    {
        return [
            'email' => new EmailUnique(Auth::id())
        ];
    }