Building forms for a settings page- looking for ideal solution

So If I am trying to build a settings page, I have many input fields spread across several pages of settings that may insert values into one of several tables. One page of settings may have several different tables being accessed.

With that said, I am trying to find the most ideal solution to build this. My options so far are standard php controllers/ blade, a livewire component, or one of the JS solutions.

Now my dilemma is that I don't want a user to have to scroll all the way to the bottom and potentially forget to save any changes in the settings if all they are doing is updating a couple random fields. So I'd really like each input, or perhaps small groups of inputs, like a first/ last name scenario, to be saved individually. Or things like username and email, or bday/genders to be disabled unless an intermediate step of do you really want to change this, is performed. Bday especially cause I don't want people just being able to change their bday at will to access things not age appropriate. I may even need to throw in a system that checks if a previously registered minor is trying to change their bday, then a proof of age will be required. but I'm not sure. Or if an adult is trying to change their age to be a minor them a flag will be sent to determine why. But that's for later.

My main concern right now is, can I have multiple smaller forms of a whole on the same page. Would all these individual forms be wrapped with duplicate form tag to the same update method? Or, could I have multiple submits on one page, all within one form tag, so which ever one is clicked will just save the current status of all fields. How will this affect my validation if a users table for instance has several rules but only a few fields are being sent through a request? I've been starting with using "filled" rule instead of required, but not sure if this is ideal.

Which would be the best setup up to allow field updates as a user navigates off the field without a page refresh or needing a submit button?

I was originally going do livewire, but read that it may not be helpful when it comes to building my mobile version of the app. So to avoid a lot of work that I would just have to redo later, I'm in the process of trying to learn Vue, but was wondering if there were any quicker solutions for this simple task, such as alpine or jQuery. without needing to make some complex setup redoing everything I currently have in blade.