Hi Stefan,
Thank you. I have since tried that, and it seems to have fixed the commands running on top of each other issue, but there are still other issues present that I can't seem to fix. There must be some issue with telnet directly, as during manual testing without LAVA, I ran some simple commands to check file contents on my DUT, and for no reason there were characters in the command that just did not get sent over and caused the command to fail, as it was no longer a valid command (for example, "cat" became "ct"). It's possible it's an issue with ser2net, but I have no idea.
Though I don't expect to be able to get much help on it, I did try using minicom as an alternative to telnet, as I found it never gave that issue (during manual testing, similar to what I mentioned before with telnet), I ran into the problem of "No cursor motion capability (cm)", and nothing I did fixed it. If there is a work around or proper solution for this please let me know.
Best regards, Michael