I know several people who are in arranged marriages, and while they are happy enough with the situation, all of them have very clearly said they will never do this to their children, so take from that what you will.
Introduction is common enough I’d say, but any expectation beyond maybe talking to them is not.
As for what most people do: it’s just going about life and meeting people. Join clubs, talk to people in your community, at work or school, friends of friends (or family friends, again introducing is common enough, anything beyond that isn’t), even bars works; anywhere really.
Just don’t go places to find a partner; go to places to meet people. From there meet the ones you like more often, make friends, and over time you’ll bump into people and find the right ones. This is one of those things that happens more the less you “try”. Be open to the idea, but let people get to know you as a friend first.
I’m not sure I understand what you’re proposing to use as a fingerprint, or what
means, however at the end of the day all server-client authentication and authorization works by passing a “password” with the request to prove who you are. Whether that’s a passkey, session token, jwt, actual password or a salted and hashed fingerprint doesn’t change where the security leak for session hijacking is: stealing whatever it is you keep passing along.
You are sending the server something to prove it’s you, and if I steal it I can pretend to be you.
This can be mitigated with short lifespans for those “passwords”, or using cryptography. However, cryptography is expensive and usually already included somewhat by using https, and short lifespans (which I think your multiple fingerprint hashes refers to?) eventually lead to poor user experience by requiring frequent logins or very quick usage because the tokens run out before they can be refreshed.