At some point, you're going to feed the entropy source into software. Having the app be part of your trusted computing base reduces the chance of a data-entry error that could leave users forever without their data.
For almost any real-world use case, memorizing the password and typing it in on a keyboard is pretty much a necessity. There are many kinds of inputs that don't allow another software like DiceKeys to enter the secret, so I'd still definitely rather stick with the simpler, human-readable option.
I'm probably an outlier, because I already have random dice, but "right leg squshr december 46 monday" seems secure enough to me: https://i.imgur.com/JGh4fik.jpg
Password crack time estimator sites are giving me times ranging from a few months to a few centuries to brute force it. Probably OK but I'd personally want something a bit better for a master password.
[1] 12 x 6^6 x 12 x 6^2 x 7 x 11! / 2. The first 5 factors come from the individual dice, the 11! covers order, and the divide by 2 comes from the two numeric d6 being interchangeable so order does not matter for them.
Under that assumption, yup. But naturally, if you were really going to do this, you wouldn't tell anyone which dice you used, or that you even used dice to generate the password. Ideally you'd probably use even more dice.
Of course, diceware is meant to use something most people can get their hands on easily; a day-of-week die, etc., isn't something you're going to find in a common game set.
[0] https://www.eff.org/deeplinks/2016/07/new-wordlists-random-p...