That happens all the time in order for a host to establish multiple connections to another host (remember that TCP does not have clients or servers; client/server is an application layer concept that is off-topic here). As RFC 793, Transmission Control Protocol explains:
The combination of this information, including sockets, sequence
numbers, and window sizes, is called a connection.
Because you have a new SYN with a different sequence number, you are creating a new connection. Things like web browsers regularly do that in order to get different parts of a web page to load at the same time.
All your example is doing is trying to create a second connection.
Edit based on your comments and answer:
The sequence of events in your question cannot be in the same connection because you have a different initial sequence number. As it explains in the RFC quote above in my answer, the sequence number is a critical part of the connection, and you are changing the initial sequence number, so it cannot be part of the same connection. The only possible explanations are that this is a new connection, which is common, or the host has a bad TCP implementation or there is some programming on the host that is purposely trying to mess up TCP, neither of those are on topic or part of the TCP protocol theory.
If the next SYN was part of the same connection, it must have the same initial sequence number, meaning your question would be the same question as the question you linked. A different initial sequence number means it is a different connection, and that happens just about every time you load a web page.
Your answer actually deals with a different question, which is about a half-open connection. Your question, based on its sequence of events, is actually about a fully open connection, and the host starting a new connection.
The TCP protocol theory is on-topic here, but a question asking an extra-theoretical question is off-topic. What a buggy host-specific implementation (a proper TCP implementation would not have a different initial sequence number for the same connection), or a purposeful attempt to disrupt TCP, does is something for a different SE site (either a host OS-specific site or Information Security).