A jail is an excellent use for a permanently internet-facing process. A process that accepts incoming data from the internet without solicitation. A process with an always-open port facing the internet. For example, an email server which waits for unsolicited port 25 connections. An exception to this generalization would be a process such as Wireguard which can sit with an "open" port facing the internet but doesn't respond to *anything* except an inquiry with the precise encryption key required to access that port; the port looks closed to any other probe. Wireguard need not be jailed.
I prefer to use the standard toolset to create and manage jails and NOT use a jail manager such as Bastille. When you master the standard toolset (it is not difficult) you will understand better what a wrapper program, such as Bastille, is doing. The standard toolset also will survive if the wrapper program subsequently isn't maintained going forward (such as happened with EZJAIL and IOCAGE).
NB: I am a hobbyist with no computer science background.