Performance impact of using virtual columns simply to house inline action buttons?

[Sarah_H]

Does anyone know off-hand if there would be a measurable performance difference between these two options?

1. Using an empty spreadsheet column to house an inline action button
2. Using a virtual column with formula "true" to house an inline action button

I am creating an app that will see heavy table view use, and some of the tables have many columns. I want to have inline action buttons next to ref_rows columns to navigate directly to the expanded ref_rows view from the table (instead of clicking to open detail view, and scrolling to the bottom to access the ref_rows table's built-in button). I don't want to attach the buttons directly to the ref_rows columns, because this will remove the header text and count values in the table view, and make it harder for users to know what they're clicking.

I have about 10-15 of these columns to create, across ~3000 records. I am hoping to create virtual columns with a "true" formula to house these buttons, because I don't have enough placeholder columns left in my tables and would have to regenerate schemas otherwise. However, I don't want to use virtual columns if it would negatively impact performance. I'm hoping that a simple "true" formula wouldn't make much of a difference?

Thank you so much for your insight!
Sarah