Rocket application with 2 cargo.toml files

Is it possible to specify 2 cargo.toml files for a single rocket application? I want to keep universal rocket dependencies outside of dependencies that users would add themselves. e.g. I would keep rocket = "0.4.2" and readiness/liveness endpoints tests in a separate cargo.toml file, which I would run first before installing dependencies in the user's cargo.toml file (where user's would put their dependencies).

Not really. Why are users modifying your cargo toml?