I feel like doubling the workload is better than quadrupling the size of the project inheriting a bevy of features and tools you likely won’t touch at all. Sure it’s stripped out later (ideally), but I like less bloat and that includes during dev when I might have to dig through 3rd party code with its own conventions and standards packed into a ‘source available’ library with potentially dogshit or absent documentation.
Also yes, it’s good practice
I handled the virtual paperwork for all leaves of absence at my last job, and there were multiple cases of medical leaves being extended indefinitely. There was something like several months to a year of extended absence before the company would even be allowed to consider firing, and other restrictions over handling medical LOA could make it almost impossible to get in contact with the employee to verify their recovery status.
Should a business be allowed to stop paying for medical coverage they promised to someone who in turn has a medical accident that puts them in a coma? Can the business legally or ethically assume they will never return or provide additional value to the company? Does your business give a shit about ethics?
You could view it as the employee gaming the system or taking advantage of a loophole, but the gray area definitely leaves more than just OP confused about what to do. In the longest case I remember, the reason they were able to stay employed for so long was nothing to do with how the employee was tolerated before leaving. From conversations, I got the impression that management would rather not have them return anyways