That check constraint won't prevent rows in tEmployeesStatus from being deleted/updated if there's a matching row in the child table. A foreign key will (or will cascade the delete/update if required)

The check constraint doesn't give the optimiser extra information about the relationship, a foreign key will.