While not "best practice", versions of this formula have been floating around for a while and can work "pretty good" for some situations.
Modify for your use case (e.g. replace "Subject" with your custom field name). Keep in mind the caveats and limitations from other comments as it is a high resource solution.
This is a formula from the Case object and creates a link to the root parent case from any child record within five levels. Adjust/reduce levels as needed.
/* First hyperlink allows sort by subject instead of ID in reports/lists */
HYPERLINK("/?sort=" +
BLANKVALUE(Parent.Parent.Parent.Parent.Parent.Subject,
BLANKVALUE(Parent.Parent.Parent.Parent.Subject,
BLANKVALUE(Parent.Parent.Parent.Subject,
BLANKVALUE(Parent.Parent.Subject,
BLANKVALUE(Parent.Subject,
Subject))))), "", '_self') +
HYPERLINK('/lightning/r/' +
BLANKVALUE(Parent.Parent.Parent.Parent.Parent.Id,
BLANKVALUE(Parent.Parent.Parent.Parent.Id,
BLANKVALUE(Parent.Parent.Parent.Id,
BLANKVALUE(Parent.Parent.Id,
BLANKVALUE(Parent.Id,
Id))))) & "/view",
BLANKVALUE(Parent.Parent.Parent.Parent.Parent.Subject,
BLANKVALUE(Parent.Parent.Parent.Parent.Subject,
BLANKVALUE(Parent.Parent.Parent.Subject,
BLANKVALUE(Parent.Parent.Subject,
BLANKVALUE(Parent.Subject,
Subject))))),"_self")
Minion__c
field? See comments on the (downvoted) answer as to why this is important. (You sort of hint at this with the final question...)